Bug 518410
Summary: | Seg fault in clustered broker where ttl is used in conjunction with lvq | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise MRG | Reporter: | Gordon Sim <gsim> | ||||
Component: | qpid-cpp | Assignee: | mick <mgoulish> | ||||
Status: | CLOSED ERRATA | QA Contact: | Jiri Kolar <jkolar> | ||||
Severity: | urgent | Docs Contact: | |||||
Priority: | urgent | ||||||
Version: | 1.1.6 | CC: | freznice, iboverma, jkolar, lbrindle, mcressma, tao | ||||
Target Milestone: | 1.2 | ||||||
Target Release: | --- | ||||||
Hardware: | All | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: |
Messaging bug fix
C: Messages with a time to live (TTL) value were sent to a last value queue (LVQ) on a clustered broker, and replaced older messages also with a TTL set
C: The broker would experience a segfault and crash.
F: This bug resulted from a partial application of svn rev 760087. Some code was omitted. The fix is to use all the code from that rev.
R: TTL messages sent to a clustered broker no longer cause crashes.
Messages with a time to live (TTL) value were sent to a last value queue (LVQ) on a clustered broker, and replaced older messages also with a TTL set. When this occurred, the broker would experience a segfault and crash. This bug occurred because some code was omitted from a patch. The entire patch has now been applied, and TTL messages sent to a clustered broker no longer cause crashes.
|
Story Points: | --- | ||||
Clone Of: | Environment: | ||||||
Last Closed: | 2009-12-03 09:17:26 UTC | Type: | --- | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Bug Depends On: | |||||||
Bug Blocks: | 527551 | ||||||
Attachments: |
|
Description
Gordon Sim
2009-08-20 09:50:21 UTC
This problem goes away in svn rev 760087. But somehow, part of Alan delta in that rev got omitted from our -26 patch to svn rev 752581. Which means that it got omitted from our 1.1.6 release. I am attaching the patch that should be applied to rev 752581 *after* the -26 patch, to fix this problem. Gordon's reproducer, in his comment above, was 100% effective for me always within 1 or 2 seconds. After this patch the problem does not recur after ten iterations of his reproducer. Created attachment 360524 [details]
patch to fix problem
this patch fixes the problem.
*** Bug 521854 has been marked as a duplicate of this bug. *** The LVQ aspect is not causal. If you just leave that out (use the same reproducer as above, but without the LVQ option) you get duplicate bug 521854. Which has the same behavior and cure as this one. Tested: on -26 bug aapears (but only on x86_64) on -28 has been fixed validated on RHEL RHEL5-Server-U4 i386 / x86_64 packages: # rpm -qa | grep -E '(qpid|openais|rhm)' | sort -u openais-0.80.6-8.el5 python-qpid-0.5.752581-3.el5 qpidc-0.5.752581-28.el5 qpidc-debuginfo-0.5.752581-28.el5 qpidc-devel-0.5.752581-28.el5 qpidc-rdma-0.5.752581-28.el5 qpidc-ssl-0.5.752581-28.el5 qpidd-0.5.752581-28.el5 qpidd-acl-0.5.752581-28.el5 qpidd-cluster-0.5.752581-28.el5 qpidd-devel-0.5.752581-28.el5 qpid-dotnet-0.4.738274-2.el5 qpidd-rdma-0.5.752581-28.el5 qpidd-ssl-0.5.752581-28.el5 qpidd-xml-0.5.752581-28.el5 qpid-java-client-0.5.751061-9.el5 qpid-java-common-0.5.751061-9.el5 rhm-0.5.3206-14.el5 rhm-docs-0.5.756148-1.el5 rh-tests-distribution-MRG-Messaging-qpid_common-1.5-15 ->VERIFIED Release note added. If any revisions are required, please set the "requires_release_notes" flag to "?" and edit the "Release Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: The clustered broker is no longer crashing when ttl is used in conjunction with lvq. This crash was occurring when messages with a ttl were sent to an lvq on a clustered broker to replace previous messages also with a ttl set (518410) Release note updated. If any revisions are required, please set the "requires_release_notes" flag to "?" and edit the "Release Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1 +1,8 @@ -The clustered broker is no longer crashing when ttl is used in conjunction with lvq. This crash was occurring when messages with a ttl were sent to an lvq on a clustered broker to replace previous messages also with a ttl set (518410)+Messaging bug fix + +C: Messages with a time to live (TTL) value were sent to a last value queue (LVQ) on a clustered broker, and replaced older messages also with a TTL set +C: The broker would experience a segfault and crash. +F: +R: + +MORE INFORMATION REQUIRED FOR RELNOTE Release note updated. If any revisions are required, please set the "requires_release_notes" flag to "?" and edit the "Release Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -2,7 +2,7 @@ C: Messages with a time to live (TTL) value were sent to a last value queue (LVQ) on a clustered broker, and replaced older messages also with a TTL set C: The broker would experience a segfault and crash. -F: -R: +F: This bug resulted from a partial application of svn rev 760087. Some code was omitted. The fix is to use all the code from that rev. +R: TTL messages sent to a clustered broker no longer cause crashes. -MORE INFORMATION REQUIRED FOR RELNOTE+Messages with a time to live (TTL) value were sent to a last value queue (LVQ) on a clustered broker, and replaced older messages also with a TTL set. When this occurred, the broker would experience a segfault and crash. This bug occurred because some code was omitted from a patch. The entire patch has now been applied, and TTL messages sent to a clustered broker no longer cause crashes. An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHEA-2009-1633.html |