Bug 476761
Summary: | When an agent is non-responsive, the qpid-config CLI utility sees long delay | ||
---|---|---|---|
Product: | Red Hat Enterprise MRG | Reporter: | Ted Ross <tross> |
Component: | qpid-qmf | Assignee: | Ted Ross <tross> |
Status: | CLOSED ERRATA | QA Contact: | Frantisek Reznicek <freznice> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 1.1 | CC: | esammons, jsarenik |
Target Milestone: | 1.1 | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2009-02-04 15:37:12 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: |
Description
Ted Ross
2008-12-16 23:23:48 UTC
This is fixed in upstream revision 727462. The fix was to make qpid-config more defensive. It now restricts its queries to involve only the agent that is co-resident with the broker-under-management. This is going to be difficult to positively verify because non-responsive agents occur only intermittently. Example scenario: Ensure qpidd is running (root# service qpidd restart) On one console, manually start sesame (root# sesame) On another console, start qpid-config (root# qpid-config) Back at console #1, press ^Z to suspend the process by shell. On second console, run qpid-config again in version python-qpid-0.3.722953 it is hanging in version python-qpid-0.4.732797 it is working* Tested on RHEL-5.2 and 4.7, both i386 and x86_64. * qpid-config will work just in case it's internal Python syntax is updated to work with older Python versions. See Bug 479382 for more info. 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-0035.html |