Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Wed, 6 Jun 2012 18:01:24 +0000 (UTC)
From: "Myrna van Lunteren (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: <1351155088.44350.1339005684453.JavaMail.jiratomcat@issues-vm>
Subject: [jira] [Commented] (DERBY-4303) Handful of replication tests failed
 because they failed to get a connection to the slave within two minutes.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

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

I believe we ran into this again, with ibm 1.5, against 10.10.0.0 alpha built at revision level 1346698:
http://people.apache.org/~myrnavl/derby_test_results/main/windows/testlog/ibm15/1346698-suites.All_diff.txt
I thought this bug was a little hard to find, but I finally found a message to the dev list by Mamta listing one of the failed tests. 

Here is the stack trace from the test output - as in the previous occurrence with 10.6, the slave's derby.log shows a BindException.
--------------------------------
testReplication_Local_TestStraightReplication(org.apache.derbyTesting.functionTests.tests.replicationTests.ReplicationRun_Local)junit.framework.AssertionFailedError: startMaster did not succeed
	at org.apache.derbyTesting.junit.BaseTestCase.fail(BaseTestCase.java:890)
	at org.apache.derbyTesting.functionTests.tests.replicationTests.ReplicationRun.startMaster_direct(ReplicationRun.java:1028)
	at org.apache.derbyTesting.functionTests.tests.replicationTests.ReplicationRun.startMaster(ReplicationRun.java:930)
	at org.apache.derbyTesting.functionTests.tests.replicationTests.ReplicationRun_Local.testReplication_Local_TestStraightReplication(ReplicationRun_Local.java:139)
	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:113)
	at org.apache.derbyTesting.functionTests.tests.replicationTests.ReplicationRun.runBare(ReplicationRun.java:246)
	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.SQLException: DERBY SQL error: SQLCODE: -1, SQLSTATE: XRE04, SQLERRMC: Could not establish a connection to the peer of the replicated database 'C:\jartest\JarResults.2012-06-05\ibm15_suites.All\db_master\wombat' on address 'localhost:3106'.
	at org.apache.derby.client.am.SQLExceptionFactory.getSQLException(Unknown Source)
	at org.apache.derby.client.am.SqlException.getSQLException(Unknown Source)
	at org.apache.derby.jdbc.ClientDataSource.getConnection(Unknown Source)
	at org.apache.derbyTesting.functionTests.tests.replicationTests.ReplicationRun.startMaster_direct(ReplicationRun.java:1008)
	... 31 more
Caused by: org.apache.derby.client.am.SqlException: DERBY SQL error: SQLCODE: -1, SQLSTATE: XRE04, SQLERRMC: Could not establish a connection to the peer of the replicated database 'C:\jartest\JarResults.2012-06-05\ibm15_suites.All\db_master\wombat' on address 'localhost:3106'.
	at org.apache.derby.client.am.Connection.completeSqlca(Unknown Source)
	at org.apache.derby.client.net.NetConnectionReply.parseRdbAccessFailed(Unknown Source)
	at org.apache.derby.client.net.NetConnectionReply.parseAccessRdbError(Unknown Source)
	at org.apache.derby.client.net.NetConnectionReply.parseACCRDBreply(Unknown Source)
	at org.apache.derby.client.net.NetConnectionReply.readAccessDatabase(Unknown Source)
	at org.apache.derby.client.net.NetConnection.readSecurityCheckAndAccessRdb(Unknown Source)
	at org.apache.derby.client.net.NetConnection.flowSecurityCheckAndAccessRdb(Unknown Source)
	at org.apache.derby.client.net.NetConnection.flowUSRIDONLconnect(Unknown Source)
	at org.apache.derby.client.net.NetConnection.flowConnect(Unknown Source)
	at org.apache.derby.client.net.NetConnection.initialize(Unknown Source)
	at org.apache.derby.client.net.NetConnection.<init>(Unknown Source)
	at org.apache.derby.client.net.ClientJDBCObjectFactoryImpl.newNetConnection(Unknown Source)
	at org.apache.derby.jdbc.ClientDataSource.getConnectionX(Unknown Source)
	... 33 more
----------------------------------------

                
> Handful of replication tests failed because they failed to get a connection to the slave within two minutes. 
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-4303
>                 URL: https://issues.apache.org/jira/browse/DERBY-4303
>             Project: Derby
>          Issue Type: Bug
>          Components: Test
>    Affects Versions: 10.6.1.0
>            Reporter: Mamta A. Satoor
>              Labels: derby_triage10_8
>         Attachments: TryReproDerby4303_diff.txt, master_and_slave_logs.zip
>
>
> The nightly runs on trunk(revision 793163) using ibm15 had 19 failures in replication tests (all failing for same reason
> junit.framework.AssertionFailedError: startMaster did not succeed.)  Copying Knut's comments to the failure
> **************
> It looks like all the failing tests failed to get a connection to the
> slave within two minutes. There may be more information in derby.log on
> the slave or on the master (should be available in the fail
> directory). It's probably best to log a JIRA issue and attach the
> information there. This is not one of the known replication test
> failures, I think, but since they all fail the same way it sounds likely
> that there is some test cleanup code that doesn't properly release all
> resources or an environment problem of some kind.
> **************

--
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