[
https://issues.apache.org/jira/browse/XMLBEANS-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12642216#action_12642216
]
pjhepworth edited comment on XMLBEANS-328 at 10/23/08 11:04 AM:
-------------------------------------------------------------------
We are also experiencing this same issue while running performance tests
against a webapp with LoadRunner.
We use XmlBeans for our domain objects which are stored in the session and
passed about through the application.
I believe that our tests should each run on a single thread, and not share
XmlObjects between sessions as each user should be logging in and creating a
new session.
Has anyone seen the above errors when not accessing an XmlObject with multiple
threads? Or are there potentially some static classes in XmlBeans that have
threading issues?
We're running with Weblogic 9.2 MP2 and XmlBeans 2.3.
was (Author: pjhepworth):
We are also experiencing this same issue while running performance tests
against a webapp with LoadRunner.
We use XmlBeans for our domain objects which are stored in the session and
passed about through the application.
I believe that our tests should each run on a single thread, and not share
XmlObjects between sessions as each user should be logging in and creating a
new session.
Has anyone seen the above errors when not accessing an XmlObject with multiple
threads? Or are there potentially some static classes in XmlBeans that have
threading issues?
> 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
> Priority: Critical
> Attachments: patch-xmlbeans-2.2.0
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
