NullPointerException when invoking statement event listeners if one of the listeners is null

• Key: DERBY-3695
• Type: Bug
• Status: Closed
• Resolution: Fixed
• Priority: Minor
• Assignee: Knut Anders Hatlen
• Reporter: Knut Anders Hatlen
• Component/s: JDBC, Network Client
• Affects Version/s: 10.4.1.3
• Fix Version/s: 10.4.2.0, 10.5.1.1

Description

If PooledConnection.addStatementEventListener() is called with a null argument, the client driver throws a NullPointerException when the listeners are invoked. Embedded does not throw an exception.

Comments

[Knut Anders Hatlen]

Attaching patch which adds a JUnit test case that reproduces the problem.

[Knut Anders Hatlen]

The attached patch adds a null check in Client{XA,Pooled}Connection40.addStatementEventListener() and makes the test case in repro.diff pass.

[Knut Anders Hatlen]

All the regression tests passed with d3695.diff.

[Knut Anders Hatlen]

Committed revision 661292.

I noticed that addConnectionEventListener() has the same mismatch between embedded and client, so I'll leave the issue open until that has been fixed too.

[Kristian Waagan]

I noticed that the remaining work mentioned for this issue, can be fixed under DERBY-3307.
Added link.

[Knut Anders Hatlen]

Merged to 10.4 and committed revision 664708.

I'm closing the issue since the remaining work can be performed as part of DERBY-3307.