db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (DERBY-3675) ConcurrentModificationException on closing pooled connection
Date Tue, 10 Jun 2008 18:37:45 GMT

     [ https://issues.apache.org/jira/browse/DERBY-3675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Knut Anders Hatlen resolved DERBY-3675.

    Resolution: Duplicate

I'm marking this issue as resolved on the assumption that it is a duplicate of DERBY-3401.
A fix for DERBY-3401 has been checked in on trunk and on the 10.4 branch.

> 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.
> 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.

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

View raw message