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:32:24 +0000 (UTC)
From: "Myrna van Lunteren (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: <600114894.44443.1339007544020.JavaMail.jiratomcat@issues-vm>
Subject: [jira] [Updated] (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:all-tabpanel ]

Myrna van Lunteren updated DERBY-4303:
--------------------------------------

    Attachment: faillogs_06062012.zip
    
> 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, faillogs_06062012.zip, 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