Federation connections initiated from windows brokers stuck in "connecting"
state
---------------------------------------------------------------------------------
Key: QPID-2199
URL: https://issues.apache.org/jira/browse/QPID-2199
Project: Qpid
Issue Type: Bug
Components: C++ Broker
Affects Versions: 0.5
Environment: Windows XP, qpid 0.5 from .msi installer, hosts scengsrv
and jlaughlin
Ubuntu Hardy, qpid 0.5 compiled from source with unused return value patches,
host santa-anna
Reporter: Jeff Laughlin
My Windows broker can't establish federation link to other brokers running on
windows or linux; links remain in "connecting" state forever. Packet sniffer
reveals strange and inconsistent things. Linux broker can successfully
establish links to windows brokers, however. Python client tools seems to work
fine with both windows and linux brokers, from both cygwin python and linux
python.
Here's a terminal session transcript that illustrates this behavior. I'm
starting with two fresh instances of qpid on two different windows hosts,
jlaughlin and scengsrv. Both have been configured with a durable alarms
exchange and durable alarmd queue that have been bound together.
First I try to create the link in push mode, so qpid-route is commanding
jlaughlin (the localhost) to establish a link to scengsrv
jlaugh...@jlaughlin ~/Downloads/qpid-0.5/python/commands
$ python2.5 qpid-route queue add scengsrv jlaughlin alarms alarmd --ack 1
--src-local
After a moment I check my links
jlaugh...@jlaughlin ~/Downloads/qpid-0.5/python/commands
$ python2.5 qpid-route link list
Host Port Transport Durable State Last Error
=============================================================================
scengsrv 5672 tcp N Connecting
Hm it's still connecting. Wait a few moments.
jlaugh...@jlaughlin ~/Downloads/qpid-0.5/python/commands
$ python2.5 qpid-route link list
Host Port Transport Durable State Last Error
=============================================================================
scengsrv 5672 tcp N Connecting
Still connecting. Darn. Lets try going the other way, commanding scengsrv to
link to jlaughlin.
jlaugh...@jlaughlin ~/Downloads/qpid-0.5/python/commands
$ python2.5 qpid-route queue add scengsrv jlaughlin alarms alarmd --ack 1
jlaugh...@jlaughlin ~/Downloads/qpid-0.5/python/commands
$ python2.5 qpid-route link list scengsrv
Host Port Transport Durable State Last Error
=============================================================================
jlaughlin 5672 tcp N Connecting
Still no good.
Now lets try commanding jlaughlin to connect to my linux box, santa-anna
jlaugh...@jlaughlin ~/Downloads/qpid-0.5/python/commands
$ python2.5 qpid-route queue add santa-anna jlaughlin alarms alarmd --ack 1
--src-local
jlaugh...@jlaughlin ~/Downloads/qpid-0.5/python/commands
$ python2.5 qpid-route link list
Host Port Transport Durable State Last Error
=============================================================================
santa-anna 5672 tcp N Connecting
jlaugh...@jlaughlin ~/Downloads/qpid-0.5/python/commands
$ python2.5 qpid-route link list
Host Port Transport Durable State Last Error
=============================================================================
santa-anna 5672 tcp N Connecting
Negative, ghost rider, the pattern is full.
Enough of this, lets command the linux host, santa-anna, to connect to my
jlaughlin windows host:
jlaugh...@jlaughlin ~/Downloads/qpid-0.5/python/commands
$ python2.5 qpid-route queue add santa-anna jlaughlin alarms alarmd --ack 1
jlaugh...@jlaughlin ~/Downloads/qpid-0.5/python/commands
$ python2.5 qpid-route link list santa-anna
Host Port Transport Durable State Last Error
=============================================================================
jlaughlin 5672 tcp N Operational
It works! Yay Linux! Still why is the windows client behaving so poorly?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
