Details
-
Bug
-
Status: Open
-
Critical
-
Resolution: Unresolved
-
Version 2.2, Version 2.2.1
-
None
-
None
-
None
-
At least Win XP and Linux 2.6 with Sun JRE. Intel multi-core processor.
Description
Running a strongly threadded Eclipse application using xmlbeans in multi-processor (/multi-core) computer causes frequent crashes in xmlbeans code.
Most of the crases happen in Cur.java in form of a NPE:
***************************************************
java.lang.NullPointerException
at org.apache.xmlbeans.impl.store.Cur.listRemove(Cur.java:2783)
at org.apache.xmlbeans.impl.store.Locale.getCur(Locale.java:2775)
at org.apache.xmlbeans.impl.store.Locale.tempCur(Locale.java:2736)
at org.apache.xmlbeans.impl.store.Locale.tempCur(Locale.java:2731)
at org.apache.xmlbeans.impl.store.Xobj.tempCur(Xobj.java:348)
at org.apache.xmlbeans.impl.store.Xobj.new_cursor(Xobj.java:1810)
at org.apache.xmlbeans.impl.values.XmlObjectBase.newCursor(XmlObjectBase.java:250)
at org.apache.xmlbeans.impl.values.XmlObjectBase.selectPath(XmlObjectBase.java:424)
at org.apache.xmlbeans.impl.values.XmlObjectBase.selectPath(XmlObjectBase.java:415)
***************************************************
In some cases the crash happens in Locale.exit():
***************************************************
Exception occurred: java.lang.ArrayIndexOutOfBoundsException: -1
at org.apache.xmlbeans.impl.store.Locale.exit(Locale.java:2840)
***************************************************
This problem problem occurs in xmlbeans 2.2. and in the latest version in SVN. The problem disappears when I turn the multi-core support off from BIOS and reappears again immediently when I turn it back on. So I believe that this has something to do with threading. Only classes Locale.java and Cur.java seem to be affected. I haven't encountered any exceptions from other classes.