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 "Bryan Pendleton (JIRA)" <de...@db.apache.org> on 2006/05/06 18:45:22 UTC

[jira] Commented: (DERBY-1298) Tracing client data source gives NPE if all data source properties are not set

    [ http://issues.apache.org/jira/browse/DERBY-1298?page=comments#action_12378229 ] 

Bryan Pendleton commented on DERBY-1298:
----------------------------------------

I agree that adding the null check is the right thing to do here. Seems like a simple, clean fix.


> Tracing client data source gives NPE if all data source properties are not set
> ------------------------------------------------------------------------------
>
>          Key: DERBY-1298
>          URL: http://issues.apache.org/jira/browse/DERBY-1298
>      Project: Derby
>         Type: Bug

>   Components: Network Client
>     Versions: 10.2.0.0, 10.1.3.0
>     Reporter: Deepa Remesh
>     Priority: Minor
>  Attachments: ClientTracing.java
>
> I found this when trying to capture client traces for another issue. If all the properties are set to some value, tracing works without problems. I will upload a repro with more details. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira