[ https://issues.jboss.org/browse/JBTM-1616?page=com.atlassian.jira.plugin.... ] Michael Musgrove commented on JBTM-1616: ---------------------------------------- That's expected if the test hung since periodic recovery is the only other activity that will be happening. The last line of the log shows that the server monitor process (CSControl.TestProcess) is about to exit but there is no entry in the log to indicate that the client was about to start, nor is there any C output indicating that the C executable (cs.c) is running - maybe the C exe is wedged in serverinit(). The test certainly never got as far as successfully starting the C client. I would definitely either debug it on a laptop or add some debug statements to indicate what the monitor process (TestProcess) read back from the launched process (it probably got end of stream on the first read but it would be handy to verify that). I would also add some debug to run_server in cs.cxx to see if it progressed passed serverinit. This extra debug is going to make the log noisy so I would be judicious in what logging I add when committing any fix. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira