History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: JRA-8442
Type: Third-party issue Third-party issue
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Mark Chaimungkalanont [Atlassian]
Reporter: Mark Chaimungkalanont [Atlassian]
Votes: 0
Watchers: 1
Operations

If you were logged in you would be able to see more operations.
JIRA

Importing data on WebSphere 5.1 causing ConcurrentModificationException

Created: 07/Nov/05 07:57 PM   Updated: 13/Mar/06 01:28 AM
Component/s: Import / Export
Affects Version/s: None
Fix Version/s: 3.4

Time Tracking:
Not Specified

File Attachments: 1. File cp1252.xtu (0.6 kb)

Environment: WebSphere 5.1
Issue Links:
Blocker
 

Participants: Anton Mazkovoi [Atlassian] and Mark Chaimungkalanont [Atlassian]
Since last comment: 130 weeks, 6 days ago
Resolution Date: 07/Nov/05 07:58 PM
Labels:


 Description  « Hide
Occassionally when importing data in WebSphere 5.1 you will see the stack trace below and the import will fail.
2005-11-07 17:39:01,057 ERROR [jira.action.admin.ImportParser] Exception importing entity null
java.util.ConcurrentModificationException
        at java.util.AbstractList$Itr.checkForComodification(AbstractList.java(Inlined Compiled Code))
        at java.util.AbstractList$Itr.remove(AbstractList.java(Compiled Code))
        at java.util.AbstractCollection.remove(AbstractCollection.java(Compiled Code))
        at com.ibm.ejs.j2c.ConnectionHandleManager.removeHandle(ConnectionHandleManager.java:187)
        at com.ibm.ejs.j2c.ConnectionHandleManager.removeHandle(ConnectionHandleManager.java:148)
        at com.ibm.ejs.j2c.ConnectionEventListener.connectionClosed(ConnectionEventListener.java:179)
        at com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl.processConnectionClosedEvent(WSRdbManagedConnectionImpl.java(Compiled Code))
        at com.ibm.ws.rsadapter.jdbc.WSJdbcConnection.closeWrapper(WSJdbcConnection.java:467)
        at com.ibm.ws.rsadapter.jdbc.WSJccConnection.closeWrapper(WSJccConnection.java:597)
        at com.ibm.ws.rsadapter.jdbc.WSJdbcObject.close(WSJdbcObject.java(Compiled Code))
        at org.ofbiz.core.entity.jdbc.SQLProcessor.close(SQLProcessor.java(Compiled Code))
        at org.ofbiz.core.entity.GenericDAO.insert(GenericDAO.java:93)
        at org.ofbiz.core.entity.GenericHelperDAO.create(GenericHelperDAO.java:63)
        at org.ofbiz.core.entity.GenericDelegator.create(GenericDelegator.java:470)
        at org.ofbiz.core.entity.GenericDelegator.create(GenericDelegator.java:450)
        at org.ofbiz.core.entity.GenericValue.create(GenericValue.java:77)
        at com.atlassian.jira.action.admin.ImportParser$1.run(ImportParser.java:188)
        at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:748)
        at java.lang.Thread.run(Thread.java:568)

This is becasue of a bug with certain version of WS as noted at http://www-1.ibm.com/support/docview.wss?rs=180&uid=swg1PQ87029

Upgrading to the specifed fix appears to resolve this issue



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Anton Mazkovoi [Atlassian] - 08/Nov/05 12:33 AM
WebSPhere 5.1 Cumulative Fix 5 resolves this problem.