Details
-
Bug
-
Status: Closed
-
Minor
-
Resolution: Fixed
-
None
-
None
Description
In the new performance test framework, the ParticipantExecutor does these two things at the end when the participant has completed:
- Send the results
- Tell the participant to release its resources.
When this is done in the order listed, the client may receive a TEAR_DOWN_TEST command, which causes the connection to be closed, while it is inside releseResources(). This provokes the client deadlock reported in QPID-4276.
Attachments
Attachments
Issue Links
- relates to
-
QPID-4276 Java client - deadlock on concurrent close of consumer and connection
- Closed