Ok,
The unicast socket didn't have a timeout set, the harness was stuck on
.join() waiting for the socket to close.
The tests still failing but it's no longer hanging.
Cheers,
Peter.
Peter Firmstone wrote:
Ok this time I've got 3 separate jvm stacks and a stack trace, and the
test is
Peter Firmstone wrote:
Ok,
The unicast socket didn't have a timeout set, the harness was stuck on
.join() waiting for the socket to close.
The tests still failing but it's no longer hanging.
Cheers,
Peter.
I set a timeout on the socket, the test fails and exits, but now I've
got a stale
Sorry, there's so much detail it's difficult to see what's going on, and
it looks like I only pasted the Server stack, oops. The test isn't
timing out as it should, I'll run it again and grab the client stack, I
killed the test after 2 hours, so the test was definitely deadlocked.
There are
Ok this time I've got 3 separate jvm stacks and a stack trace, and the
test is deadlocked (cpu idle):
[java] Running
com/sun/jini/test/spec/lookupdiscovery/MulticastMonitorStopReplace.td
[java] Time is Sat Nov 24 16:47:24 EST 2012
[java] Starting test in separate process with
