Back to bug 790390

Who When What Removed Added
ppecka 2012-02-20 12:37:15 UTC Version 2.1 Development
Justin Ross 2012-02-22 16:30:46 UTC CC jross
Assignee rhm-maint-list tross
Target Milestone 2.1.2 2.2
Flags needinfo?(tross)
Irina Boverman 2012-06-11 20:45:56 UTC Target Milestone 2.2 2.3
Frantisek Reznicek 2012-08-22 09:36:08 UTC CC freznice
Leonid Zhaldybin 2012-08-23 15:00:51 UTC CC lzhaldyb
Irina Boverman 2012-10-14 18:07:45 UTC CC iboverma
Assignee tross kgiusti
Flags needinfo?(tross) needinfo?(kgiusti)
Irina Boverman 2012-10-18 18:14:50 UTC Keywords TestBlocker
Priority unspecified medium
Severity unspecified high
Justin Ross 2012-10-24 19:58:48 UTC Flags needinfo?(kgiusti)
Justin Ross 2012-10-24 23:05:04 UTC Status NEW ASSIGNED
Target Milestone 2.3 2.4
Justin Ross 2013-02-22 18:41:34 UTC Flags needinfo?(kgiusti)
Ken Giusti 2013-02-22 19:40:39 UTC Flags needinfo?(kgiusti)
Ken Giusti 2013-04-16 15:56:01 UTC Status ASSIGNED MODIFIED
Fixed In Version qpid-0.18
Ken Giusti 2013-06-12 15:17:58 UTC Doc Text Cause: When the broker performs a shutdown, it cleans up all resources it maintains for each connected client. Should a client issue a management request to the broker during this shutdown processing, a race condition exists which could cause the processing of the request to conflict with the shutdown process.

Consequence: The internal resources of the broker are corrupted, which can result in a crash.

Fix: Locking was added to prevent the request processing thread from accessing resources that were being deleted by the shutdown process.

Result: The internal resources remain consistent during the clean up process - no corruption occurs.
Eric Sammons 2013-07-10 13:35:40 UTC Target Milestone 2.4 3.0
Ernie 2013-08-08 15:25:34 UTC CC eallen
QA Contact mrgqe-bugs eallen
Ernie 2013-08-12 20:23:09 UTC Status MODIFIED VERIFIED
Stanislav Graf 2013-10-26 11:55:28 UTC Keywords TestBlocker
Jared MORGAN 2014-09-15 00:07:08 UTC Doc Text Cause: When the broker performs a shutdown, it cleans up all resources it maintains for each connected client. Should a client issue a management request to the broker during this shutdown processing, a race condition exists which could cause the processing of the request to conflict with the shutdown process.

Consequence: The internal resources of the broker are corrupted, which can result in a crash.

Fix: Locking was added to prevent the request processing thread from accessing resources that were being deleted by the shutdown process.

Result: The internal resources remain consistent during the clean up process - no corruption occurs.
When the broker performed a shutdown, it cleaned up all resources it maintained for each connected client. If a client issued a management request to the broker during shutdown processing, a race condition existed which caused request processing to conflict with the shutdown process. This caused the internal resources of the broker to become corrupted, which could have resulted in a crash. Locking was added to prevent the request processing thread from accessing resources that were being deleted by the shutdown process. The internal resources remain consistent during the clean up process, and no corruption occurs.
errata-xmlrpc 2014-09-24 14:41:36 UTC Status VERIFIED RELEASE_PENDING
errata-xmlrpc 2014-09-24 15:03:59 UTC Status RELEASE_PENDING CLOSED
Resolution --- ERRATA
Last Closed 2014-09-24 11:03:59 UTC

Back to bug 790390