db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alan Burlison (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-4225) EmbeddedConnectionPoolDataSource40 never calls the ConnectionEventListener calbacks
Date Tue, 12 May 2009 18:42:45 GMT

    [ https://issues.apache.org/jira/browse/DERBY-4225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12708558#action_12708558
] 

Alan Burlison commented on DERBY-4225:
--------------------------------------

Thanks for the offer, but before I impose on your time I need to do some more digging in the
application.  I've found one place where the exception thrown by a close without a prior commit
or rollback is ignored, there may be others.  If I fix all those and I still get the problem,
I'll update the bug. Thanks!

> EmbeddedConnectionPoolDataSource40 never calls the ConnectionEventListener calbacks
> -----------------------------------------------------------------------------------
>
>                 Key: DERBY-4225
>                 URL: https://issues.apache.org/jira/browse/DERBY-4225
>             Project: Derby
>          Issue Type: Bug
>          Components: JDBC
>    Affects Versions: 10.5.1.1
>         Environment: Solaris
>            Reporter: Alan Burlison
>            Priority: Blocker
>         Attachments: ConnectionPoolTest.java
>
>
> I'm using EmbeddedConnectionPoolDataSource40 to implement a simple connection pool. 
A skeleton of the code looks like this:
> ----------
> class PoolConnectionEventListener implements ConnectionEventListener {
>    ...
> }
> :
> EmbeddedConnectionPoolDataSource40 source =  new EmbeddedConnectionPoolDataSource40();
> :
> connListener = new PoolConnectionEventListener();
> :
> PooledConnection conn = pconn.getConnection();
> conn.addConnectionEventListener(connListener);
> ----------
> This is so I can catch the connectionClosed and connectionErrorOccurred events and recycle
the connections.  In Derby 10.4.2.1 this all works fine, in 10.5.1.1 it doesn't work at all
- the callbacks never get made.  This makes 10.5.1.1 unusable in anything that uses connection
pooling, such as a JNDI context.
> I haven't checked ClientConnectionPoolDataSource40, it may have the same problem.

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


Mime
View raw message