[DERBY-3675] ConcurrentModificationException on closing pooled connection

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 10.4.1.3
• Component/s: Network Client
• Urgency: Normal
• Assignee: Unassigned
• Reporter: Trejkaz
• Created: 15/May/08 04:13
• Updated: 21/Jan/11 17:51
• Resolved: 10/Jun/08 18:37

Description

I'm seeing the following exception from calling close() on a connection returned from a CollectionPoolDataSource.

java.util.ConcurrentModificationException
at java.util.AbstractList$Itr.checkForComodification(AbstractList.java:372)
at java.util.AbstractList$Itr.next(AbstractList.java:343)
at org.apache.derby.client.ClientPooledConnection.recycleConnection(ClientPooledConnection.java:343)
at org.apache.derby.client.am.LogicalConnection.close(LogicalConnection.java:83)

The only particularly unique thing about the area of the code where we're doing this is that we're closing it immediately after opening it, as an initial check to make sure it can connect.

Issue Links

• duplicates: DERBY-3401 Removing a ConnectionEventListener from a PooledConnection during its connectionClosed() callback causes other ConnectionEventListener callbacks to be missed
• relates to: DERBY-3401 Removing a ConnectionEventListener from a PooledConnection during its connectionClosed() callback causes other ConnectionEventListener callbacks to be missed