QpidTestCase does not ensure failed brokers are fully stopped.
--------------------------------------------------------------
Key: QPID-2033
URL: https://issues.apache.org/jira/browse/QPID-2033
Project: Qpid
Issue Type: Bug
Components: Java Tests
Reporter: Martin Ritchie
When an external broker fails to become ready within the alloted 30 seconds
QpidTestCase simply runs the clean script and logs the error.
In the case of the Java broker it is possible that the process has started up
and bound to the Management port then failed in a hung state. As a result QTC
does not see the READY statement and assumes the broker has died.
Yet it does not kill the process to ensure it is really gone.
This results in all subsequent test runs failing with 'broker failed to be come
ready' errors and in a CI situation all test runs will stop as the rogue
process will not be terminated.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
