[ 
https://issues.apache.org/jira/browse/DERBY-6143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13656185#comment-13656185
 ] 

Myrna van Lunteren commented on DERBY-6143:
-------------------------------------------

I ran this test 100 times ( including a number of times concurrently) on the 
machine where this failure is seen most frequently, but the failure did not 
reproduce.
However, it *did* fail again on May 9, 10.10.1.2 - (1480861), with ibm 1.7 and 
1.6. 
(see: 
http://people.apache.org/~myrnavl/derby_test_results/v10_10/windows/testSummary-1480861.html).
 
ibm 1.6 actually saw 2 failures in DerbyLayerATest, 
cs_FailedStreamInsertCharBufferBoundaries (with a IOException) and 
cs_StreamInsertCharBufferBoundary(SQLNonTransientConnectionException)
Note that ibm 1.5 failed with a different error, and all failed around the same 
time (ca 22.40 PDT. )
Which is about the same time as on May 6 and May 1, and April 1. (I don't have 
the old results from before that time so I cannot say about those earlier 
failures).

I checked the Event logs on this machine, but there's nothing special happening 
at that time as far as I can tell from those logs.
This is however a virtual (vmware) machine, so it's possible that there's 
unusual activity happening on the vmware server at that time, causing network 
trouble. I will ask the systems 
administrator people investigate that aspect.
However, these tests kick off every day more or less at the same time, so if 
there's some regular activity happening, why would this fail sometimes, and 
sometimes 
pass? Also, as these tests run through suites.All in the same sequence every 
day, obviously, if they are going to fail, they'll fail around the same time 
each day, so the timing may be a red herring.

Is there possibly something we can do with the test to protect from this type 
of failure?"

                
> 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.9.2.2, 10.10.1.2, 10.11.0.0
>         Environment: windows, ibm15, 10.10 candidate branch
>            Reporter: Mike Matrigali
>            Assignee: Myrna van Lunteren
>
> 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

Reply via email to