[
https://issues.apache.org/jira/browse/DERBY-5643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13233822#comment-13233822 ]
Mike Matrigali commented on DERBY-5643:
---------------------------------------
got 7 failures in nightly tests on ibm16 and ibm17. are these the kinds of problems you expect to be fixed by changes in this JIRA? If so I won't bother to open a new JIRA:
http://people.apache.org/~myrnavl/derby_test_results/main/windows/testlog/ibm16/1301855-derbyall_diff.txthttp://people.apache.org/~myrnavl/derby_test_results/main/windows/testlog/ibm17/1301855-derbyall_diff.txt
> 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
> Assignee: Knut Anders Hatlen
> Fix For: 10.9.0.0
>
> Attachments: fail-on-timeout.diff, higher-timeout.diff, 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.jspaFor more information on JIRA, see:
http://www.atlassian.com/software/jira
