db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-4303) Handful of replication tests failed because they failed to get a connection to the slave within two minutes.
Date Tue, 21 Jul 2009 00:35:14 GMT

     [ https://issues.apache.org/jira/browse/DERBY-4303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Kathey Marsden updated DERBY-4303:
----------------------------------

    Attachment: TryReproDerby4303_diff.txt

I think I may have been wrong about the ports not getting set uniquely  for replication. 
The attached patch (not for commit) has just the three tests that use getAlternativePort().
 What happens is the ports for replication get set first because they are set are set with
static fields but they do seem to be different than the ones used for the other tests.  The
patch  also forces an exception in ttestSetPortPriority() and that does not interfere with
the subsequent replication tests, so more investigation is needed.


> 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.0.0
>            Reporter: Mamta A. Satoor
>         Attachments: master_and_slave_logs.zip, TryReproDerby4303_diff.txt
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message