You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Knut Anders Hatlen (JIRA)" <ji...@apache.org> on 2008/06/10 15:10:45 UTC
[jira] Resolved: (DERBY-3307) NPE in PooledConnction event
notification handling if a null listener is added
[ https://issues.apache.org/jira/browse/DERBY-3307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Knut Anders Hatlen resolved DERBY-3307.
---------------------------------------
Resolution: Fixed
Fix Version/s: 10.4.1.4
Merged to 10.4 and committed revision 666094.
> NPE in PooledConnction event notification handling if a null listener is added
> ------------------------------------------------------------------------------
>
> Key: DERBY-3307
> URL: https://issues.apache.org/jira/browse/DERBY-3307
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.3.2.1, 10.4.1.3
> Reporter: Kristian Waagan
> Assignee: Knut Anders Hatlen
> Priority: Minor
> Fix For: 10.4.1.4, 10.5.0.0
>
> Attachments: d3307.diff, derby-3307-1a-test_repro.diff
>
>
> If a null reference is passed in to one of the ClientPooledConnection.addXEventListener, a NPE will be thrown if an event occurs.
> I will attach a simple repro as a patch to the test jdbc4.StatementEventsTests. I believe the situation is the same for connection event listeners.
> I have found no information in the specs regarding null listeners, but I assume it would be okay to ignore them.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.