[ http://issues.apache.org/jira/browse/DERBY-1777?page=comments#action_12431609 ] A B commented on DERBY-1777: ----------------------------
> There are 15 other queries that fail. Do all of them fail with the same error and same stack trace? Or are the failures different? When the queries fail, is there anything in the derby.log file that might indicate a problem? Also, for the most recent query that you posted, what are the expected results? I ran the most recently-posted query in client/server mode against 10.1.2 (before any optimizer changes went in), 10.2 beta (the latest), and 10.3 (with some early changes that I have for DERBY-1315). In all cases the query compiles and executes without error. I think this means that the problem isn't so much the specific query as it is the state of the client/server communication at the time these queries are executed. That in turn suggests that the series of events preceding the failed statements are somehow related to the failures, or else perhaps that some other error occured in the Derby engine and that error causes problems in the client/server communication. To help track the latter, add the property: derby.stream.error.logSeverityLevel=0 and then check derby.log to see if there are any errors recorded when the failure occurs. To help track the former (client/server communication) it would be great if you could enable client and server tracing and then post the traces to this issue (NOTE: these traces can be somewhat large). For info on how to enable client/server tracing, see: http://wiki.apache.org/db-derby/ProtocolDebuggingTips I don't know how much of that is possible in your environment, but the more info you can provide about Derby status at the time of the failure, the better. Hopefully these initial steps can provide some insight.... > 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 > Fix For: 10.2.1.0 > > > 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
