[
https://issues.apache.org/jira/browse/DERBY-4303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733323#action_12733323
]
Kathey Marsden commented on DERBY-4303:
---------------------------------------
So I think I see 3 (maybe 4) problems.
1) ttestSetPortPriority intermittently fails for some reason with the bind
error which we should track down. (When we fail with the bind error we also
get an NPE getting the a message. I am not sure if this is the root cause or
another issue.)
2) If ttestSetPortPriority fails for some reason it does not clean up the
servers it has started.
3) The replication tests should be using different ports than
ttestSePortPriority but seem to be using the same ones.
Addressing any of the three I think would resolve the multiple replication
failures.
I think I will start by looking at 3 because I should at least be able to
reproduce that in my environment.
> 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.
