[
https://issues.apache.org/jira/browse/DERBY-5643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13225969#comment-13225969
]
Kristian Waagan commented on DERBY-5643:
----------------------------------------
I see that the handling of sub-process streams isn't optimal in ReplicationRun.
This may lead to problems as in DERBY-5608. It would be good to fix this once
further investigation has been carried out.
> 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
>
>
> 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
