db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Deepa Remesh (JIRA)" <derby-...@db.apache.org>
Subject [jira] Updated: (DERBY-1298) Tracing client data source gives NPE if all data source properties are not set
Date Wed, 24 May 2006 14:21:30 GMT
     [ http://issues.apache.org/jira/browse/DERBY-1298?page=all ]

Deepa Remesh updated DERBY-1298:
--------------------------------

    Attachment: derby-1298.diff

Attaching a patch 'derby-1298.diff' which adds a check for null value before calling setProperty
in org.apache.derby.client.am.LogWriter. With this patch, I checked that the repro does not
give NPE. I also ran derbynetclientmats with Sun jdk 1.4.2 on Windows XP. Please take a look.
Thanks.

> 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
>     Reporter: Deepa Remesh
>     Assignee: Deepa Remesh
>     Priority: Minor
>      Fix For: 10.2.0.0
>  Attachments: ClientTracing.java, derby-1298.diff
>
> 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


Mime
View raw message