|
View:
New views
12 Messages
—
Rating Filter:
Alert me
|
|
|
[jira] Created: (XMLBEANS-328) Problems in multi-processor environmentProblems 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 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: dev-unsubscribe@... For additional commands, e-mail: dev-help@... |
|
|
[jira] Updated: (XMLBEANS-328) Problems in multi-processor environment[ https://issues.apache.org/jira/browse/XMLBEANS-328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cezar Andrei updated XMLBEANS-328: ---------------------------------- Pasi, it seems that you are the first to find this problem. Please make sure you don't use XMLOptions.setUnsynchronized(), so that XmlBeans can take care of the synchronization. Assuming there is a bug, it is very had to find it without reproducing it and having only the two stack traces you're attached. To help us finding the bug, we need to make sure what revision number are your sources at and that you don't have any changes, the full stack traces, plus the smallest XMLBeans user code that reproduces the problem. > 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 > > 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: dev-unsubscribe@... For additional commands, e-mail: dev-help@... |
|
|
[jira] Commented: (XMLBEANS-328) Problems in multi-processor environment[ https://issues.apache.org/jira/browse/XMLBEANS-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12504741 ] Matthieu Baechler commented on XMLBEANS-328: -------------------------------------------- We have the same problem here, with a multithreaded software running on a SMP computer. I didn't managed to extract a short test case to reproduce this problem at will, but my software is a good test case. Anyway, I think I found the origin of this threading problem, see the patch attached below. Review welcome. > 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 > > 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: dev-unsubscribe@... For additional commands, e-mail: dev-help@... |
|
|
[jira] Updated: (XMLBEANS-328) Problems in multi-processor environment[ https://issues.apache.org/jira/browse/XMLBEANS-328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthieu Baechler updated XMLBEANS-328: --------------------------------------- Attachment: patch-xmlbeans-2.2.0 This patch is for xmlbeans 2.2.0. You can manually apply the fix on xmlbeans 2.3.0 (tested here). > 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: dev-unsubscribe@... For additional commands, e-mail: dev-help@... |
|
|
[jira] Commented: (XMLBEANS-328) Problems in multi-processor environment[ https://issues.apache.org/jira/browse/XMLBEANS-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12626202#action_12626202 ] Damon Jacobsen commented on XMLBEANS-328: ----------------------------------------- I would like to bump this issue. I am getting it as well and do not see the ifx in the upcoming 2.4 release. > 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: dev-unsubscribe@... For additional commands, e-mail: dev-help@... |
|
|
[jira] Commented: (XMLBEANS-328) Problems in multi-processor environment[ https://issues.apache.org/jira/browse/XMLBEANS-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12629430#action_12629430 ] Joakim Sandstroem commented on XMLBEANS-328: -------------------------------------------- I'm experiencing the same type of problem using xbean-2.2.0.jar 2008-09-09 10:48:11,025 ERROR [STDERR] [:] org.apache.xmlbeans.XmlException: -1 2008-09-09 10:48:11,025 ERROR [STDERR] [:] at org.apache.xmlbeans.XmlBeans.wrappedException(XmlBeans.java:149) 2008-09-09 10:48:11,025 ERROR [STDERR] [:] at org.apache.xmlbeans.XmlBeans.compileXmlBeans(XmlBeans.java:675) 2008-09-09 10:48:11,025 ERROR [STDERR] [:] at org.apache.xmlbeans.XmlBeans.compileXsd(XmlBeans.java:553) 2008-09-09 10:48:11,025 ERROR [STDERR] [:] at com.eviware.soapui.impl.wsdl.support.xsd.SchemaUtils.buildSchemaTypes(SchemaUtils.java:233) 2008-09-09 10:48:11,025 ERROR [STDERR] [:] at com.eviware.soapui.impl.wsdl.support.xsd.SchemaUtils.loadSchemaTypes(SchemaUtils.java:172) 2008-09-09 10:48:11,026 ERROR [STDERR] [:] at com.eviware.soapui.impl.wsdl.support.wsdl.WsdlContext.loadDefinitions(WsdlContext.java:256) 2008-09-09 10:48:11,026 ERROR [STDERR] [:] at com.eviware.soapui.impl.wsdl.support.wsdl.WsdlContext.access$500(WsdlContext.java:53) 2008-09-09 10:48:11,026 ERROR [STDERR] [:] at com.eviware.soapui.impl.wsdl.support.wsdl.WsdlContext$Loader.construct(WsdlContext.java:210) 2008-09-09 10:48:11,026 ERROR [STDERR] [:] at com.eviware.soapui.support.swing.SwingWorkerDelegator.construct(SwingWorkerDelegator.java:45) 2008-09-09 10:48:11,026 ERROR [STDERR] [:] at com.eviware.soapui.support.swing.SwingWorker$2.run(SwingWorker.java:111) 2008-09-09 10:48:11,026 ERROR [STDERR] [:] at java.lang.Thread.run(Thread.java:619) 2008-09-09 10:48:11,026 ERROR [STDERR] [:] Caused by: java.lang.ArrayIndexOutOfBoundsException: -1 2008-09-09 10:48:11,026 ERROR [STDERR] [:] at org.apache.xmlbeans.impl.store.Locale.exit(Locale.java:2879) 2008-09-09 10:48:11,026 ERROR [STDERR] [:] at org.apache.xmlbeans.impl.store.Xobj.fetch_text(Xobj.java:1800) 2008-09-09 10:48:11,043 ERROR [STDERR] [:] at org.apache.xmlbeans.impl.values.XmlObjectBase.get_wscanon_text(XmlObjectBase.java:1332) 2008-09-09 10:48:11,043 ERROR [STDERR] [:] at org.apache.xmlbeans.impl.values.XmlObjectBase.check_dated(XmlObjectBase.java:1269) 2008-09-09 10:48:11,043 ERROR [STDERR] [:] at org.apache.xmlbeans.impl.values.JavaIntegerHolder.bigIntegerValue(JavaIntegerHolder.java:58) 2008-09-09 10:48:11,043 ERROR [STDERR] [:] at org.apache.xmlbeans.impl.values.XmlObjectBase.getBigIntegerValue(XmlObjectBase.java:1504) 2008-09-09 10:48:11,043 ERROR [STDERR] [:] at org.apache.xmlbeans.impl.schema.StscComplexTypeResolver.extractMinOccurs(StscComplexTypeResolver.java:1187) 2008-09-09 10:48:11,043 ERROR [STDERR] [:] at org.apache.xmlbeans.impl.schema.StscComplexTypeResolver.translateContentModel(StscComplexTypeResolver.java:1303) 2008-09-09 10:48:11,043 ERROR [STDERR] [:] at org.apache.xmlbeans.impl.schema.StscComplexTypeResolver.translateContentModel(StscComplexTypeResolver.java:1427) 2008-09-09 10:48:11,043 ERROR [STDERR] [:] at org.apache.xmlbeans.impl.schema.StscComplexTypeResolver.resolveCcRestriction(StscComplexTypeResolver.java:419) 2008-09-09 10:48:11,043 ERROR [STDERR] [:] at org.apache.xmlbeans.impl.schema.StscComplexTypeResolver.resolveComplexType(StscComplexTypeResolver.java:234) 2008-09-09 10:48:11,043 ERROR [STDERR] [:] at org.apache.xmlbeans.impl.schema.StscResolver.resolveType(StscResolver.java:87) 2008-09-09 10:48:11,043 ERROR [STDERR] [:] at org.apache.xmlbeans.impl.schema.StscResolver.resolveAll(StscResolver.java:59) 2008-09-09 10:48:11,044 ERROR [STDERR] [:] at org.apache.xmlbeans.impl.schema.SchemaTypeSystemCompiler.compileImpl(SchemaTypeSystemCompiler.java:307) 2008-09-09 10:48:11,044 ERROR [STDERR] [:] at org.apache.xmlbeans.impl.schema.SchemaTypeSystemCompiler.compile(SchemaTypeSystemCompiler.java:218) 2008-09-09 10:48:11,044 ERROR [STDERR] [:] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 2008-09-09 10:48:11,044 ERROR [STDERR] [:] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) 2008-09-09 10:48:11,044 ERROR [STDERR] [:] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) 2008-09-09 10:48:11,044 ERROR [STDERR] [:] at java.lang.reflect.Method.invoke(Method.java:597) 2008-09-09 10:48:11,044 ERROR [STDERR] [:] at org.apache.xmlbeans.XmlBeans.compileXmlBeans(XmlBeans.java:667) 2008-09-09 10:48:11,044 ERROR [STDERR] [:] ... 9 more 2008-09-09 10:48:11,044 ERROR [STDERR] [:] org.apache.xmlbeans.XmlException: -1 2008-09-09 10:48:11,058 ERROR [STDERR] [:] at org.apache.xmlbeans.XmlBeans.wrappedException(XmlBeans.java:149) > 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: dev-unsubscribe@... For additional commands, e-mail: dev-help@... |
|
|
[jira] Commented: (XMLBEANS-328) Problems in multi-processor environment[ https://issues.apache.org/jira/browse/XMLBEANS-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12642216#action_12642216 ] Paul Hepworth commented on XMLBEANS-328: ---------------------------------------- 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: dev-unsubscribe@... For additional commands, e-mail: dev-help@... |
|
|
[jira] Issue Comment Edited: (XMLBEANS-328) Problems in multi-processor environment[ 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: dev-unsubscribe@... For additional commands, e-mail: dev-help@... |
|
|
[jira] Updated: (XMLBEANS-328) Problems in multi-processor environment[ https://issues.apache.org/jira/browse/XMLBEANS-328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radu Preotiuc-Pietro updated XMLBEANS-328: ------------------------------------------ Attachment: xbean.jar Mathieu's patch synchronizes methods in Xobj.java, but that class should be kept unsynchronized so I moved the synchronization up in the call chain in XmlObjectBase.java Since so many people have hit this, I would appreciate you guys trying out this re-written patch and letting me know if it works. If it does, I will check it in. I am attaching a pre-built jar with the patch applied on top of XMLBeans 2.4.0 release, I will also attach the source tomorrow so it can be built against most other versions. > 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, 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. - You can reply to this email to add a comment to the issue online. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@... For additional commands, e-mail: dev-help@... |
|
|
[jira] Updated: (XMLBEANS-328) Problems in multi-processor environment[ https://issues.apache.org/jira/browse/XMLBEANS-328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radu Preotiuc-Pietro updated XMLBEANS-328: ------------------------------------------ Attachment: patch-XMLBEANS328-2.4.0.patch The patch in source form, as promised. Again, for everyone who has commented on this, your help is needed to see if this patch resolves your issues. Many thanks. > 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, 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. - You can reply to this email to add a comment to the issue online. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@... For additional commands, e-mail: dev-help@... |
|
|
[jira] Commented: (XMLBEANS-328) Problems in multi-processor environment[ https://issues.apache.org/jira/browse/XMLBEANS-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12771409#action_12771409 ] Chuck Kasek commented on XMLBEANS-328: -------------------------------------- I was seeing this error in a project I am working on. I had multiple threads each processing the same message over and over, and was seeing a failure rate of about .5% (i.e. approx. 25 messages out of 5000 would fail). After switching to the xbean.jar that Radu provided, I have not seen the error recur, having processed my message over 130,000 times, using the same test case as before. > 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, 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. - You can reply to this email to add a comment to the issue online. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@... For additional commands, e-mail: dev-help@... |
|
|
[jira] Assigned: (XMLBEANS-328) Problems in multi-processor environment[ https://issues.apache.org/jira/browse/XMLBEANS-328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wing Yew Poon reassigned XMLBEANS-328: -------------------------------------- Assignee: Radu Preotiuc-Pietro > 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. - You can reply to this email to add a comment to the issue online. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@... For additional commands, e-mail: dev-help@... |
| Free embeddable forum powered by Nabble | Forum Help |