[ http://issues.apache.org/jira/browse/DERBY-1430?page=comments#action_12421885 ] Mayuresh Nirhali commented on DERBY-1430: -----------------------------------------
On further analysis, I am getting sure that this failure is due to server instance being dropped prematurely before completion of the test. I suspect tht, initially when the client tries to connect to a Server thread, it does not connect to the newly created thread, but instead gets hooked to the already running thread. This thread then exits before the test is complete and hence this failure is seen. It is very difficult to reproduce this bug in the exact setup where it is seen (nightly test runs). Similar errors have been observed for couple of tests that are run after this particular test which are, junitTests/derbyNet/CompatibilityTest.java jdbcapi/xaSimplePositive.sql Occasionally, the test before parameterMapping.java have found to be failed with java.net.ConnectException : Error connecting to server .... see test reports for 9th July. The operating platform is SolX86 and this issue is not seen on any other platform. > Test parameterMapping.java often fails with DerbyNetClient on Solarisx86 > ------------------------------------------------------------------------ > > Key: DERBY-1430 > URL: http://issues.apache.org/jira/browse/DERBY-1430 > Project: Derby > Issue Type: Bug > Components: Regression Test Failure > Affects Versions: 10.2.0.0 > Environment: derbyall on Solaris x86. > Reporter: Øystein Grøvlen > Fix For: 10.2.0.0 > > Attachments: derby.log > > > parameterMapping.java has lately failed about every other day in the nightly > test on Solaris x86. First time seen on June 4. (Note that the computer > that this is run on has had its disk cache turned off lately. Maybe there is > a connection?) The test gets the following exception: > FAIL unexpected exception - (58009):Insufficient data while reading from the > network - expected a minimum of 6 bytes and received only -1 bytes. The > connection has been terminated.java.sql.SQLException: Insufficient data while > reading from the network - expected a minimum of 6 bytes and received only -1 > bytes. The connection has been terminated. > 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.apache.derbyTesting.functionTests.tests.jdbcapi.parameterMapping.main(Unknown > Source) > Caused by: org.apache.derby.client.am.DisconnectException: Insufficient data > while reading from the network - expected a minimum of 6 bytes and received > only -1 bytes. The connection has been terminated. > at org.apache.derby.client.net.Reply.fill(Unknown Source) > at org.apache.derby.client.net.Reply.ensureALayerDataInBuffer(Unknown > Source) > at org.apache.derby.client.net.Reply.readDssHeader(Unknown Source) > at org.apache.derby.client.net.Reply.startSameIdChainParse(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) > ... 2 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
