[ http://issues.apache.org/jira/browse/DERBY-1777?page=all ]
A B updated DERBY-1777:
-----------------------
Attachment: d1777_v2.patch
Attaching a second version of the patch, d1777_v2.patch, that includes a test
case for catching regressions of the first NPE described above. As mentioned
in previous comments, I don't think it's going to be possible to add a test
case for the second NPE because it's intermittent and time-sensitive (and does
not reproduce with "noTimeout=true").
Aside from the new test case in lang/predicatePushdown.sql, the _v2 patch is
identical to the _v1 patch. The patch is actually quite small--only about 10
lines of actual code changes. The rest is comments and test case/master
updates.
Any review comments and/or commit would be greatly appreciated.
> Regression: query works in 10.1.2.1 but fails with NullPointerException in
> 10.2.1.1
> -----------------------------------------------------------------------------------
>
> Key: DERBY-1777
> URL: http://issues.apache.org/jira/browse/DERBY-1777
> Project: Derby
> Issue Type: Bug
> Environment: WinXP SP2 dualcore 2.8 GHz 2 GBmemory
> Reporter: Prasenjit Sarkar
> Assigned To: A B
> Fix For: 10.2.1.0
>
> Attachments: Aperi.zip, d1777_v1.patch, d1777_v2.patch, Derby1777.zip
>
>
> However, here's a query that works in 10.1.2.1 but not in 10.2.1.1 --
> database can be assumed to be the same in Derby - 1205
> 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
> Same db as before.
> In 10.2.1.1 it gives the following error (should this be a new issue?)
> 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 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
