[
https://issues.apache.org/jira/browse/DERBY-5643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13227371#comment-13227371
]
Knut Anders Hatlen commented on DERBY-5643:
-------------------------------------------
In the latest test cycle, the compatibility tests hung on one of the platforms
where we've seen hangs in the replication tests, so the problem doesn't seem to
be specific to the replication tests.
I found this bug report, which seems to match what we're seeing with
createServerSocket() taking more than three minutes:
http://bugs.sun.com/view_bug.do?bug_id=6483406
The bug is fixed in Java 7, which is consistent with what we're seeing in the
nightlies (I have only found occurrences with Java 5 and Java 6).
Perhaps we could work around this problem in the tests by increasing the
timeout for server startup to more than 3 minutes. Since we stop waiting as
soon as the server is up, this shouldn't slow down test execution unless there
actually is a problem with starting the server.
> Occasional hangs in replication tests on Linux
> ----------------------------------------------
>
> Key: DERBY-5643
> URL: https://issues.apache.org/jira/browse/DERBY-5643
> Project: Derby
> Issue Type: Bug
> Components: Replication, Test
> Affects Versions: 10.9.0.0
> Reporter: Knut Anders Hatlen
> Attachments: thread-dump.txt, waitFor-2.diff, waitFor.diff
>
>
> We occasionally see hangs in the replication tests on Linux. For example
> here:
> http://dbtg.foundry.sun.com/derby/test/Daily/jvm1.6/testing/testlog/sles/1298470-suitesAll_diff.txt
> This test run was stuck in tearDown() after
> ReplicationRun_Local_Derby4910.testSlaveWaitsForMaster(). (Waiting for
> Thread.join() to return.)
--
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
