db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Trejkaz (JIRA)" <j...@apache.org>
Subject [jira] Created: (DERBY-3675) ConcurrentModificationException on closing pooled connection
Date Thu, 15 May 2008 04:13:55 GMT
ConcurrentModificationException on closing pooled connection

                 Key: DERBY-3675
                 URL: https://issues.apache.org/jira/browse/DERBY-3675
             Project: Derby
          Issue Type: Bug
          Components: Network Client
    Affects Versions:
            Reporter: Trejkaz

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

	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.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message