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] Updated: (DERBY-3513) NullPointerException in newBrokeredStatement in app server environment
Date Tue, 11 Mar 2008 20:08:46 GMT

     [ https://issues.apache.org/jira/browse/DERBY-3513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Kathey Marsden updated DERBY-3513:
----------------------------------

    Attachment: derby-3513_diff.txt

A gave the user a patched derby.jar that just changed the newBrokeredStatement code to
hold the jdbcLevel in a local variable.
With the patch they were not able to reproduce 
the error so this small change  may serve as a workaround to a probable JIT issue.

Unfortunately because of their complex environment, it is difficult to perform JIT diagnostics
and get this resolved from the JVM side, so the
user has requested that we check in the change, 
so that they can move forward. I wonder if there are
any objections to checking in this change.  I'll plan to check in Thursday if I don't hear
back.

The NullPointer failure happened with 30-40% of the builds in a complex build then test environment
for an Application Server based system.  It could not be reproduced outside of the build-test
environment shown below :

org.apache.derby.tools.sysinfo
------------------ Java Information ------------------
Java Version:    1.5.0
Java Vendor:     IBM Corporation
Java home:       /opt/MyServer/java/jre
Java classpath:  /opt/MyServer/derby/lib/derby.jar
OS name:         Linux
OS architecture: x86
OS version:      2.6.9-55.ELsmp
Java user name:  builduser
Java user home:  /home/wsbuild
Java user dir:   /opt/MyServer/derby
java.specification.name: Java Platform API Specification
java.specification.version: 1.5
--------- Derby Information --------
JRE - JDBC: J2SE 5.0 - JDBC 3.0

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