[ http://issues.apache.org/jira/browse/DERBY-1430?page=comments#action_12420882 ]
Mayuresh Nirhali commented on DERBY-1430: ----------------------------------------- Here is my analysis on this issue so far: This bug is seen on jdbcapi/parameterMapping.java (in DerbyNetClient framework) test *inconsistently so far. I have run this test in standalone manner several times in last few days and have not seen this failure even once. I tried running the derbynetclientmats suite and have seen the exact failure only once. The platform here is identical to the one specified in JIRA entry, SolX86,v10 with jvm1.5. However, I could reproduce this failure in standalone manner while my machine is running derbynetclientmats suite simulteneously. Here, I suspect some sort of race condition between clients trying to connect to server listening at port 1527. Another type of error similar to the one mentioned in JIRA entry can also be observed for the same test, when the test is run in this scenario. The other error seen is as below, <snip> > 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. > 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. > ... 2 more Test Failed. </snip> I also looked at the test report history and found that the exact error was seen on June 2nd (r411220) first, but with a different test. A lot of other tests have failed since then due to same issue. This means that this issue is not particular to the test, paramaterMapping.java. In the recent past, this issue is seen only with the test, parameterMapping.java, but inconsistently. Also, this seems to happen only when bunch of tests (suite) is run in DerbyNetClient framework. I haven't got to the root cause of this yet. I would like to understand how does the harness handle client requests ? Can 2 requests be active/valid in any way at a time ?? any pointers on harness design would be very helpful. any inputs on what other info could help and how to gather ?? > Test parameterMapping.java often fails with DerbyNetClient on Solarisx86 > ------------------------------------------------------------------------ > > Key: DERBY-1430 > URL: http://issues.apache.org/jira/browse/DERBY-1430 > Project: Derby > Type: Bug > Components: Regression Test Failure > 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
