[jira] Commented: (DERBY-4225) EmbeddedConnectionPoolDataSource40 never calls the ConnectionEventListener calbacks

["Alan Burlison (JIRA)" <ji...@apache.org>]

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

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

Hmm, that could be related but I'm not seeing any exceptions thrown by the close calls.  According to DERBY-3319 & the release notes, if I close a connection with uncommitted changes I should get an exception with a SQLState 25001, correct?  I'm not seeing any exceptions, the close seems to complete but the underlying event listener calls never get made.

I'll carry on digging, I can provide instructions on how to pull the app in question from our repo if required, the only prerequisite is a copy of NetBeans, when the NB project is opened and run the app creates and deploys a new DB.

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