[
https://issues.apache.org/jira/browse/DERBY-5643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Knut Anders Hatlen updated DERBY-5643:
--------------------------------------
Attachment: waitFor.diff
The call that takes three minutes is ServerSockedFactory.createServerSocket().
I notice that the replication test cases wait until they see EOF on stdout and
stderr from the forked processes. However, they do not actually check that the
forked processes have terminated before they continue. Maybe this causes a
problem if the old server process hasn't completely released all resources when
the new server process starts.
The attached patch adds a call to Process.waitFor() after the streams have been
exhausted. It might be unrelated, but I'm running ReplicationSuite in a loop
now to see if it helps.
> 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.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
