db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Myrna van Lunteren (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-4303) Handful of replication tests failed because they failed to get a connection to the slave within two minutes.
Date Mon, 20 Jul 2009 17:39:14 GMT

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

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

I think that remark was off - I was looking at the time when the directories got created in
the fail directory - which doesn't reflect the time for the time-out of the startserver, but
the time for the entire test. And the replication tests take considerable time also when passing.

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