Re: [Exist-open] Concurrent xpath query exception

[Wolfgang M. <me...@if...>]

Were you using the 0.9.1 release? In this case I would suggest you retry with 
the current development snapshot. There have been several bug fixes 
addressing concurrency issues. Otherwise, could you please send me the 
logging output of the server (not the client), so we can see where the error 
occurrs in the source? And perhaps your test setup?

Wolfgang

On Tuesday 29 July 2003 12:03 am, Devrim Ergel wrote:
> Hello,
>
> We were using xindice as XML DB, but we had out of memory exception while
> retrieving xpath result of 1000 files, 3kb each. Yesterday we read that
> eXist was more capable on memory management. Then we tried the similar
> tests with embedded java clients:
>
> Server Configuration:
> 1 collection and 1200 files, each 3kb. Config.xml isn't being changed
> (default). Intel P4. 1.4 256 mb.
>
> First Test: 1 client retrieve all (1200) files after xpath result
>                 Result: Xpath results are retrieved.
>                             Test passed.
>
> Second Test: 2 clients concurrently retrieve all (1200) files after xpath
> result. Result: Xpath results are retrieved.
>                                 Test passed.
>
> Third Test:     3 clients concurrently retrieve all (1200) files after
> xpath result. Result: 1 client retrieved xpath results.  Others client had
> an exception (copied below). Test failure!
>
> For 3 and more concurrent huge query, we had that exception:
> ---------------------------------------------------------------------------
>----------------------------------------------
> org.xmldb.api.base.XMLDBException: java.lang.Exception:
> org.exist.EXistException: Internal: Internal error: element state is zero.
> at org.exist.xmldb.XMLResourceImpl.getContent(XMLResourceImpl.java:108) at
> Test.<init>(Test.java:76)
>         at Test.main(Test.java:95)
> Caused by: org.apache.xmlrpc.XmlRpcException: java.lang.Exception:
> org.exist.EXistException: Internal: Internal error: element state is zero.
> at org.apache.xmlrpc.XmlRpcClient$Worker.execute(Unknown Source) at
> org.apache.xmlrpc.XmlRpcClient.execute(Unknown Source)
>         at
> org.exist.xmldb.XMLResourceImpl.getContent(XMLResourceImpl.java:106) ... 2
> more
> ---------------------------------------------------------------------------
>---------------------------------------------
>
> We searched mail-list for that exception and we couln't find any trace. Did
> anybody make similar tests? Do we had to do a config setting? In other case
> isn't it a bug?