db-derby-dev mailing list archives

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

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

Stan Bradbury commented on DERBY-3513:
--------------------------------------

Kathey - Please DO commit this change to the 10.1 codeline afterall.  The customer experiencing
the failure has continued to test with your patch (in 11 builds to date) and has only observed
the NPE failure once (on 3/12/08).  The failure rate prior to this change was 35% (a failure
approximately every 3 builds).  Your patch, if not correcting the problem, has at least greatly
reduced the frequency with which it happens.  I will post to this issue should another build
encounter the NPE problem.  If there are no further occurrences I think it is safe to say
that the failure reported on 3/12 was an anomaly.   



> 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