db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-3513) NullPointerException in newBrokeredStatement in app server environment
Date Wed, 19 Mar 2008 23:14:24 GMT

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

Kathey Marsden commented on DERBY-3513:
---------------------------------------

OK then, I will go ahead and commit it, but I fear it will only make the problem more elusive
and hard to reproduce.  When they get to the point that they are able to run JIT diagnostics
it might make sense to test with the earlier build where it is easier to reproduce.


> NullPointerException in newBrokeredStatement in app server environment
> ----------------------------------------------------------------------
>
>                 Key: DERBY-3513
>                 URL: https://issues.apache.org/jira/browse/DERBY-3513
>             Project: Derby
>          Issue Type: Bug
>          Components: JDBC
>    Affects Versions: 10.1.3.2
>         Environment: Java Version:    1.5.0
> Java Vendor:     IBM Corporation
> OS name:         Linux
> OS architecture: x86
> OS version:      2.6.9-55.ELsmp
>            Reporter: Kathey Marsden
>            Assignee: Kathey Marsden
>         Attachments: derby-3513_diff.txt
>
>
> User reports in an app server environment an intermittent  NullPointerException
> with the 10.1 trace:
>  R java.lang.NullPointerException
> org.apache.derby.iapi.jdbc.BrokeredConnection.newBrokeredStatement(BrokeredConnection.java:448)
>    
> ...org.apache.derby.jdbc.XAStatementControl.<init>(XAStatementControl.java:62)
       
> ...org.apache.derby.jdbc.EmbedXAConnection.wrapStatement(EmbedXAConnection.java:827)
 
> org.apache.derby.iapi.jdbc.BrokeredConnection.createStatement(BrokeredConnection.java:296)
>  [snip user trace]
> The code at line 448 is simply:
> return new BrokeredStatement(statementControl, getJDBCLevel());
> so not much room for an NPE there.   I added println statements to identify the state
values and where the NPE is actually occurring but that seemed to make the 
> problem go away.  It may be a JIT issue.
> I gave them the fix for DERBY-2142 and that did not correct the problem.

-- 
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