Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 844655

Summary: error message logged while creating federation link between standalone brokers
Product: Red Hat Enterprise MRG Reporter: Petr Matousek <pematous>
Component: qpid-cppAssignee: messaging-bugs <messaging-bugs>
Status: CLOSED UPSTREAM QA Contact: MRG Quality Engineering <mrgqe-bugs>
Severity: medium Docs Contact:
Priority: low    
Version: DevelopmentCC: jross
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: 2025-02-10 03:20:23 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:
Attachments:
Description Flags
test reproducer none

Description Petr Matousek 2012-07-31 09:49:59 UTC 
Description of problem:

While creating a federated link between two non-clustered brokers, following error message is logged to the broker log:

2012-07-27 17:56:30 error Execution exception: not-found: Exchange not found: amq.failover (qpid/broker/ExchangeRegistry.cpp:97)

According to Bug 835628, Comment 6:
Even though it has logged an error, there really is nothing wrong with the broker at this point - the bind fails, the session ends and both sides clean up.

I think no error message shall be appear in the broker log.

Version-Release number of selected component (if applicable):
qpid-cpp-*-14-19

How reproducible:
100%

Steps to Reproduce:
1. start standalone broker b1
2. start standalone broker b2
3. create fed.link between the two brokers b1 and b2
  
Actual results:
An error message appears in the broker log

Expected results:
No error message appears in the broker log file

Additional info:
Comment 1 Petr Matousek 2012-07-31 09:54:06 UTC 
Created attachment 601497 [details]
test reproducer
Comment 3 Red Hat Bugzilla 2025-02-10 03:20:23 UTC 
This product has been discontinued or is no longer tracked in Red Hat Bugzilla.