db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Oliver <moli...@corenttech.com>
Subject Unsubscribe
Date Mon, 11 Jun 2012 22:34:20 GMT
Sent from my iPhone

On Jun 12, 2012, at 6:30 AM, "Myrna van Lunteren (JIRA)"
<jira@apache.org> wrote:

>
>    [ https://issues.apache.org/jira/browse/DERBY-5800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13293140#comment-13293140
]
>
> Myrna van Lunteren commented on DERBY-5800:
> -------------------------------------------
>
>    I've been unable to reproduce these at will, and using the same basePort as I used
before has passed on rerun, so unlikely that was the cause of the problem. It seems to be
intermittent.
>
>> test failure in AutoloadTest; AssertionFailedError: Test process failed:Spawned caused
by SQLNonTransientConnectionException - Software caused connection abort: recv failed.
>> -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>>
>>                Key: DERBY-5800
>>                URL: https://issues.apache.org/jira/browse/DERBY-5800
>>            Project: Derby
>>         Issue Type: Bug
>>         Components: Test
>>   Affects Versions: 10.9.1.0
>>           Reporter: Myrna van Lunteren
>>
>> I've seen a couple of these during my testing of the 10.9.1 release candidate.
>> On AIX I saw 4 issues with this test; on rerun, it seemed to be intermittent.
>> It seemed to go better when I used -Xmx512M, and also it seems using -Dderby.tests.basePort
interfered, so perhaps I was using ports already in use on the system - I'll check on that
when all other testing is complete.
>> This example is from a Windows 2008 ibm 1.6 run, where there was just 1 failure:
>> spawnProcess:JDBCDriversEmbeddedTest(org.apache.derbyTesting.functionTests.tests.jdbcapi.AutoloadTest)junit.framework.AssertionFailedError:
Test process failed:Spawned org.apache.derbyTesting.functionTests.tests.jdbcapi.JDBCDriversEmbeddedTest
exitCode=1
>> STDOUT:
>> ...........F...
>> Time: 5.312
>> There was 1 failure:
>> 1) testExplicitLoad(org.apache.derbyTesting.functionTests.tests.jdbcapi.AutoloadTest)junit.framework.ComparisonFailure:
Unexpected SQL state. expected:<0800[4]> but was:<0800[6]>
>>    at org.apache.derbyTesting.junit.BaseJDBCTestCase.assertSQLState(BaseJDBCTestCase.java:853)
>>    at org.apache.derbyTesting.junit.BaseJDBCTestCase.assertSQLState(BaseJDBCTestCase.java:896)
>>    at org.apache.derbyTesting.functionTests.tests.jdbcapi.AutoloadTest.testUnsuccessfulConnect(AutoloadTest.java:414)
>>    at org.apache.derbyTesting.functionTests.tests.jdbcapi.AutoloadTest.explicitLoad(AutoloadTest.java:457)
>>    at org.apache.derbyTesting.functionTests.tests.jdbcapi.AutoloadTest.testExplicitLoad(AutoloadTest.java:426)
>>    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
>>    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
>>    at org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:113)
>>    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: java.sql.SQLNonTransientConnectionException: A communications error has
been detected: Software caused connection abort: recv failed.
>>    at org.apache.derby.client.am.SQLExceptionFactory40.getSQLException(Unknown Source)
>>    at org.apache.derby.client.am.SqlException.getSQLException(Unknown Source)
>>    at org.apache.derby.jdbc.ClientDriver.connect(Unknown Source)
>>    at java.sql.DriverManager.getConnection(DriverManager.java:379)
>>    at java.sql.DriverManager.getConnection(DriverManager.java:415)
>>    at org.apache.derbyTesting.functionTests.tests.jdbcapi.AutoloadTest.testUnsuccessfulConnect(AutoloadTest.java:409)
>>    ... 33 more
>> Caused by: org.apache.derby.client.am.DisconnectException: A communications error
has been detected: Software caused connection abort: recv failed.
>>    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.NetConnectionReply.readExchangeServerAttributes(Unknown
Source)
>>    at org.apache.derby.client.net.NetConnection.readServerAttributesAndKeyExchange(Unknown
Source)
>>    at org.apache.derby.client.net.NetConnection.flowServerAttributesAndKeyExchange(Unknown
Source)
>>    at org.apache.derby.client.net.NetConnection.flowUSRIDPWDconnect(Unknown Source)
>>    at org.apache.derby.client.net.NetConnection.flowConnect(Unknown Source)
>>    at org.apache.derby.client.net.NetConnection.<init>(Unknown Source)
>>    at org.apache.derby.client.net.NetConnection40.<init>(Unknown Source)
>>    at org.apache.derby.client.net.ClientJDBCObjectFactoryImpl40.newNetConnection(Unknown
Source)
>>    ... 37 more
>> Caused by: java.net.SocketException: Software caused connection abort: recv failed
>>    at java.net.SocketInputStream.read(SocketInputStream.java:140)
>>    ... 49 more
>
> --
> This message is automatically generated by JIRA.
> If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
> For more information on JIRA, see: http://www.atlassian.com/software/jira
>
>

Mime
View raw message