Re: [bdbxml] Crash in dbxml_javaJNI.XmlResults_next__SWIG_0

George Feinberg wrote:
> You should share a single XmlManager and open XmlContainer
> object among threads, and only close when the application is
> exiting.

Hi George,
I rewrote the Testcase so that all Threads are using the same
XMLManager and XMLContainer objects
(see 
ftp://ftp.suse.com/pub/people/freitag/dbxml/MultithreadingTestCase.java).
The db is now created inline.
Unfortunately the error still happens in
[libdbxml_java-2.1.so+0x23ae0a] 
Java_com_sleepycat_dbxml_dbxml_1javaJNI_XmlResults_1next_1_1SWIG_10+0xb0 .


> 
> Regards,
> 
> George
> 
>> Hi, we are using dbxml from the Java interface in a multithreaded
>> environment. (Tomcat Servlet Container)
>> I am experiencing the problem that the Java JNI code crashes
>> at calling XmlResults.next() when there are some threads querying
>> concurrently on the same database. The database contains about
>> 3000 rather little documents.
>> I have extracted a test-case and the stacktrace of the crash,  
>> available at:
>> ftp://ftp.suse.com/pub/people/freitag/dbxml/MutithreadingTestCase.java
>> ftp://ftp.suse.com/pub/people/freitag/dbxml/hs_err_pid9916.log
>> Dbxml version is 2.1.8.
>> Does anyone know something about this issue?
>>
> 
> 
> 
> ------------------------------------------
> To remove yourself from this list, send an
> email to xml-unsubscribe-E1rGyZxLSgzby3iVrkZq2A-XMD5yJDbdMReXY1tMh2IBg@public.gmane.org
> 
> 



------------------------------------------
To remove yourself from this list, send an
email to [email protected]