[jira] [Created] (DERBY-6143) nightly regression test failure: cs_FailedStreamInsertCharBufferBoundaries(org.apache.derbyTesting.functionTests.tests.jdbcapi.Derby2017LayerATest)java.io.IOException

["Mike Matrigali (JIRA)" <ji...@apache.org>]

Mike Matrigali created DERBY-6143:
-------------------------------------

             Summary: nightly regression test failure: cs_FailedStreamInsertCharBufferBoundaries(org.apache.derbyTesting.functionTests.tests.jdbcapi.Derby2017LayerATest)java.io.IOException
                 Key: DERBY-6143
                 URL: https://issues.apache.org/jira/browse/DERBY-6143
             Project: Derby
          Issue Type: Bug
          Components: Test
    Affects Versions: 10.10.1.2
         Environment: windows, ibm15, 10.10 candidate branch
            Reporter: Mike Matrigali


windows, ibm15, 10.10 candidate branch
http://people.apache.org/~myrnavl/derby_test_results/v10_10/windows/testlog/ibm15/1463364-suites.All_diff.txt
There was 1 error:
1) cs_FailedStreamInsertCharBufferBoundaries(org.apache.derbyTesting.functionTests.tests.jdbcapi.Derby2017LayerATest)java.io.IOException
	at org.apache.derby.client.am.ClobLocatorReader.readCharacters(Unknown Source)
	at org.apache.derby.client.am.ClobLocatorReader.read(Unknown Source)
	at java.io.BufferedReader.fill(BufferedReader.java:157)
	at java.io.BufferedReader.read(BufferedReader.java:178)
	at org.apache.derbyTesting.junit.BaseTestCase.assertEquals(BaseTestCase.java:430)
	at org.apache.derbyTesting.functionTests.tests.jdbcapi.Derby2017LayerATest.doInsertTest(Derby2017LayerATest.java:575)
	at org.apache.derbyTesting.functionTests.tests.jdbcapi.Derby2017LayerATest.cs_FailedStreamInsertCharBufferBoundaries(Derby2017LayerATest.java:166)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:117)
	at org.apache.derbyTesting.junit.BaseJDBCTestCase.runBareOverridable(BaseJDBCTestCase.java:424)
	at org.apache.derbyTesting.junit.BaseJDBCTestCase.runBare(BaseJDBCTestCase.java:441)
	at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
	at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
	at junit.extensions.TestSetup.run(TestSetup.java:25)
	at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
	at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
	at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
	at junit.extensions.TestSetup.run(TestSetup.java:25)
Caused by: org.apache.derby.client.am.DisconnectException: A communications error has been detected: Connection reset.
	at org.apache.derby.client.net.NetAgent.throwCommunicationsFailure(Unknown Source)
	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.readExecuteCall(Unknown Source)
	at org.apache.derby.client.net.StatementReply.readExecuteCall(Unknown Source)
	at org.apache.derby.client.net.NetStatement.readExecuteCall_(Unknown Source)
	at org.apache.derby.client.am.Statement.readExecuteCall(Unknown Source)
	at org.apache.derby.client.am.PreparedStatement.flowExecute(Unknown Source)
	at org.apache.derby.client.am.PreparedStatement.executeX(Unknown Source)
	at org.apache.derby.client.am.CallableLocatorProcedures.clobGetLength(Unknown Source)
	at org.apache.derby.client.am.Clob.getLocatorLength(Unknown Source)
	at org.apache.derby.client.am.Lob.sqlLength(Unknown Source)
	... 42 more
Caused by: java.net.SocketException: Connection reset
	at java.net.SocketInputStream.read(SocketInputStream.java:197)
	... 55 more

FAILURES!!!
Tests run: 15048,  Failures: 0,  Errors: 1

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira