[DERBY-4225] EmbeddedConnectionPoolDataSource40 never calls the ConnectionEventListener calbacks

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Invalid
• Affects Version/s: 10.5.1.1
• Component/s: JDBC
• Environment: Solaris
• Urgency: Blocker
• Bug behavior facts: Regression
• Assignee: Unassigned
• Reporter: Alan Burlison
• Created: 12/May/09 09:09
• Updated: 14/Jul/09 17:23
• Resolved: 14/May/09 22:59

Description

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.

Issue Links

• relates to: DERBY-3319 Logical connections do not check if a transaction is active on close