Bug 985880 - Error message after durable link recovery
Summary: Error message after durable link recovery
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: qpid-cpp
Version: 3.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: messaging-bugs
QA Contact: Messaging QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-07-18 12:27 UTC by Leonid Zhaldybin
Modified: 2025-02-10 03:28 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2025-02-10 03:28:05 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Leonid Zhaldybin 2013-07-18 12:27:56 UTC
Description of problem:
If a durable link is created on a broker, after broker is restarted, the link gets restored from the journal successfully. It is fully functional, but qpid-route tool displays the last error message:

[root@lzhaldyb-rhel64x ~]# qpid-route link list

Host            Port    Transport Durable  State             Last Error
=============================================================================
10.34.33.229    5672    tcp          Y     Operational       Unsupported transport type: tcp (/builddir/build/BUILD/qpid-0.22/cpp/src/qpid/broker/Broker.cpp:1234

There are two problems I see here:
1) Why the process of durable link recovery is accompanied by the error?
2) This error message does not make any sense. The tcp is a supported transport type.

Version-Release number of selected component (if applicable):
qpid-cpp-0.22-7

How reproducible:
100%

Steps to Reproduce:
1. Connect two brokers with a durable federation route:
qpid-config add exchange topic fed.ex --durable --broker <src_broker>
qpid-config add exchange topic fed.ex --durable --broker <dst_broker>
qpid-config add exchange queue dest.q --durable --broker <dst_broker>
qpid-config bind fed.ex dest.q key <dst_broker>
qpid-route route add <dst_broker> <src_broker> fed.ex key --durable
2. Restart the destination broker.
3. Send some messages to the source broker's fed.ex exchange using the key 'key'.

Actual results:
The messages get federated to the destination broker properly. The 'qpid-route link list' command, however, shows the last error "Unsupported transport type: tcp".

Expected results:
no 'last error' reported as a result of durable link recovery.

Additional info:
The error message from the broker's log:
[root@lzhaldyb-rhel64x ~]# grep -i error /var/lib/qpidd/qpidd.log 
2013-07-18 12:24:05 [Broker] error Link connection to 10.34.33.229:5672 failed: Unsupported transport type: tcp (/builddir/build/BUILD/qpid-0.22/cpp/src/qpid/broker/Broker.cpp:1234)
If the source broker is restarted, the error message says "Connection refused".

Comment 2 Red Hat Bugzilla 2025-02-10 03:28:05 UTC
This product has been discontinued or is no longer tracked in Red Hat Bugzilla.


Note You need to log in before you can comment on or make changes to this bug.