[ 
https://issues.apache.org/jira/browse/XMLBEANS-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13642747#comment-13642747
 ] 

Daniel Ewing edited comment on XMLBEANS-328 at 4/26/13 11:09 AM:
-----------------------------------------------------------------

Can anyone please provide an update on this threading defect?  Is it fixed in 
any release build of xbean.jar?  If not, what would it take to get this on the 
schedule for being fixed?  It sure seems likely that it is a fairly simple 
issue of unsynchronized access to a map causing the exception.
                
      was (Author: dew...@opentext.com):
    Can anyone please provide an update on this threading defect?  Is it fixed 
in any release build of xbean.jar?  If not, what would it take to get this on 
the schedule for being fixed?  It sure likely that it is a fairly simple issue 
of unsynchronized access to a map causing the exception.
                  
> Problems in multi-processor environment
> ---------------------------------------
>
>                 Key: XMLBEANS-328
>                 URL: https://issues.apache.org/jira/browse/XMLBEANS-328
>             Project: XMLBeans
>          Issue Type: Bug
>    Affects Versions: Version 2.2, Version 2.2.1
>         Environment: At least Win XP and Linux 2.6 with Sun JRE. Intel 
> multi-core processor.
>            Reporter: Pasi Lehtimaki
>            Assignee: Radu Preotiuc-Pietro
>            Priority: Critical
>         Attachments: patch-xmlbeans-2.2.0, patch-XMLBEANS328-2.4.0.patch, 
> xbean.jar
>
>
> 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. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@xmlbeans.apache.org
For additional commands, e-mail: dev-h...@xmlbeans.apache.org

Reply via email to