Bug 982553
Summary: | Qpid don't initiate a failover on federation link when source broker don't respond but tcp is established | ||
---|---|---|---|
Product: | Red Hat Enterprise MRG | Reporter: | Zdenek Kraus <zkraus> |
Component: | qpid-cpp | Assignee: | Andrew Stitcher <astitcher> |
Status: | CLOSED WONTFIX | QA Contact: | Messaging QE <messaging-qe-bugs> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 2.4 | CC: | gtaylor, jross, pmoravec, wbirkhea, zkraus |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2020-05-22 14:35:02 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Zdenek Kraus
2013-07-09 09:41:37 UTC
Pavel, sorry for delayed response. tested with qpid-cpp-0.30-8 the broker do a "failover" but since in the scenario is only one source-broker, it is trying that one, which it is correct behaviour I think. the problem in this scenarion is that route state within that link is still treated as Operatinoal even though it can't connect to a source broker. # qpid-route link list guest/guest.37.193:5672 Host Port Transport Durable State Last Error ============================================================================= 10.34.37.192 5672 tcp N Operational Closed by peer also I hit one moment when state was Waiting, then it jumped back to Operational, while source broker was SIGSTOPped. so after SIGCONT the source broker, link is apparently established, and qpid-route still show Operational and last error closed by peer, so I would say, it's only matter of confusion in QMF. I can confirm that after source broker is enabled to run again and link is established, messages are passing through it. As I'm reviewing this issue, I now think it could be only problem in qpid-route. I'm also for lowering the severity of this issue. |