db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Waagan (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-3307) NPE in PooledConnction event notification handling if a null listener is added
Date Tue, 03 Jun 2008 13:00:44 GMT

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

Kristian Waagan commented on DERBY-3307:
----------------------------------------

Note that the existing repro ('derby-3307-1a-test_repro.diff') only tests the statement event
listener case, which has already been fixed (see DERBY-3695).
Another repro / test should be written for a connection event listener.

> 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
>            Priority: Minor
>         Attachments: 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.


Mime
View raw message