PK45777: JAVA.SQL.SQLEXCEPTION: DERBY SQL ERROR: SQLCODE: -1, SQLSTATE: XJ001 DUE TO NULLPOINTEREXCEPTION.

Java SDK 1.5 SR8 Cumulative Fix for WebSphere Application Server
Java SDK 1.5 SR8 Cumulative Fix for WebSphere Application Server
Java SDK 1.5 SR10 Cumulative Fix for WebSphere Application Server
6.1.0.31: Java SDK 1.5 SR11 FP1 Cumulative Fix for WebSphere Application Server
6.1.0.33: Java SDK 1.5 SR12 FP1 Cumulative Fix for WebSphere
6.1.0.29: Java SDK 1.5 SR11 Cumulative Fix for WebSphere Application Server
6.1.0.35: Java SDK 1.5 SR12 FP2 Cumulative Fix for WebSphere
6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server

APAR status

• Closed as program error.

Error description

• There is a bug identified in Derby 10.2.1.1; the symptom is that
  this exception is logged
  java.sql.SQLException: DERBY SQL error: SQLCODE: -1, SQLSTATE:
  XJ001, SQLERRMC: java.lang.NullPointerExceptionXJ001.U
  at org.apache.derby.client.am.SQLExceptionFactory.
    getSQLException(Unknown Source)
  at org.apache.derby.client.am.SqlException.getSQLException
    (Unknown Source)
  at org.apache.derby.client.am.Connection.prepareStatement
    (Unknown Source)
  at org.eclipse.aperi.server.guireq.topology.views.ViewerSanL1.
    init(ViewerSanL1.java:1828)
  at org.eclipse.aperi.server.guireq.topology.views.ViewerInit.
    init(ViewerInit.java:41)
  at org.eclipse.aperi.server.guireq.topology.views.ViewerInit.
    main(ViewerInit.java:69)
  .
  Caused by: org.apache.derby.client.am.SqlException: DERBY SQL
  error: SQLCODE: -1, SQLSTATE: XJ001, SQLERRMC:
  java.lang.NullPointerExceptionXJ001.U
  at org.apache.derby.client.am.Statement.completeSqlca(Unknown
    Source)
  at org.apache.derby.client.net.NetStatementReply.
    parsePrepareError(Unknown Source)
  at org.apache.derby.client.net.NetStatementReply.
    parsePRPSQLSTTreply(Unknown Source)
  at org.apache.derby.client.net.NetStatementReply.
    readPrepareDescribeOutput(Unknown Source)
  at org.apache.derby.client.net.StatementReply.
    readPrepareDescribeOutput(Unknown Source)
  at org.apache.derby.client.net.NetStatement.
    readPrepareDescribeOutput_(Unknown Source)
  at org.apache.derby.client.am.Statement.
    readPrepareDescribeOutput(Unknown Source)
  at org.apache.derby.client.am.PreparedStatement.
    readPrepareDescribeInputOutput(Unknown Source)
  at org.apache.derby.client.am.PreparedStatement.
    flowPrepareDescribeInputOutput(Unknown Source)
  at org.apache.derby.client.am.PreparedStatement.prepare(Unknown
    Source)
  at org.apache.derby.client.am.Connection.prepareStatementX
    (Unknown Source)
  ... 4 more
  .
     This is the Derby-1277 bug.
  .
     The SQL query that causes this problem is
  SELECT DISTINCT
  ZONE.ZONE_ID ZONE_ID,
  PORT.PORT_ID PORT_ID,
  ENTITY_TO_PORT.TYPE,
  ENTITY_TO_PORT.PREFIX_ID,
  ENTITY_TO_PORT.ENTITY_ID,
  ENTITY_TO_PORT.DISPLAY_NAME,
  ENTITY_TO_PORT.PORT_DISPLAY_NAME,
  PORT2ZONE.MEMBER_NAME,
  PORT2ZONE.ZONE_MEMBER_ID,
  PORT.PORT_NUMBER
  FROM
  T_RES_ZONE ZONE left outer join T_VIEW_PORT2ZONE PORT2ZONE on
  ZONE.ZONE_ID = PORT2ZONE.ZONE_ID left outer join T_RES_PORT PORT
  on
  PORT2ZONE.PORT_ID = PORT.PORT_ID left outer join
  T_VIEW_ENTITY_TO_PORT ENTITY_TO_PORT on
  PORT2ZONE.PORT_ID = ENTITY_TO_PORT.PORT_ID and
  PORT2ZONE.ZONE_ID = ENTITY_TO_PORT.ZONE_ID, T_RES_FABRIC FABRIC
  WHERE PORT2ZONE.ZONE_ID = ZONE.ZONE_ID and
  ZONE.FABRIC_WWN = FABRIC.FABRIC_WWN and
  FABRIC.FABRIC_ID = 1
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: IBM WebSphere Application Server version     *
  *                 6.1 users of WebSphere Process Server who    *
  *                 also use the derby database driver           *
  ****************************************************************
  * PROBLEM DESCRIPTION: It is possible to get an sql            *
  *                      exception when using derby with         *
  *                      Process Server                          *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  It is possible for Process Server users to see the following
  exception:
  Java.sql.sqlexception: derby sql error: sqlcode: -1, sqlstate:
  xj001 due to nullpointerexception.
  

Problem conclusion

• This apar provides an update to the derby database driver
  
  The fix for this APAR is currently targeted for inclusion
  in fixpack 6.1.0.11.
  Please refer to the recommended updates page for delivery
  information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Modules/Macros

• CLOUDSCP
  

Fix information

• Fixed component name

  WEBSPH APP SERV

• Fixed component ID

  5724J0800

Applicable component levels

• R61A PSY

     UP

• R61H PSY

     UP

• R61I PSY

     UP

• R61P PSY

     UP

• R61S PSY

     UP

• R61W PSY

     UP

• R61Z PSY

     UP