You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Jeff Laughlin (JIRA)" <qp...@incubator.apache.org> on 2009/11/13 18:15:39 UTC
[jira] Created: (QPID-2199) Federation connections initiated from
windows brokers stuck in "connecting" state
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
jlaughlin@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
jlaughlin@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.
jlaughlin@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.
jlaughlin@jlaughlin ~/Downloads/qpid-0.5/python/commands
$ python2.5 qpid-route queue add scengsrv jlaughlin alarms alarmd --ack 1
jlaughlin@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
jlaughlin@jlaughlin ~/Downloads/qpid-0.5/python/commands
$ python2.5 qpid-route queue add santa-anna jlaughlin alarms alarmd --ack 1 --src-local
jlaughlin@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
jlaughlin@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:
jlaughlin@jlaughlin ~/Downloads/qpid-0.5/python/commands
$ python2.5 qpid-route queue add santa-anna jlaughlin alarms alarmd --ack 1
jlaughlin@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:dev-subscribe@qpid.apache.org
[jira] Updated: (QPID-2199) Federation connections initiated from
windows brokers stuck in "connecting" state
Posted by "Jeff Laughlin (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-2199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jeff Laughlin updated QPID-2199:
--------------------------------
Attachment: windows.out
linux.out
Trace files captured during unsuccessful link establishment attempt with windows broker initiating a push link to the linux broker
> 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
> Attachments: linux.out, windows.out
>
>
> 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
> jlaughlin@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
> jlaughlin@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.
> jlaughlin@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.
> jlaughlin@jlaughlin ~/Downloads/qpid-0.5/python/commands
> $ python2.5 qpid-route queue add scengsrv jlaughlin alarms alarmd --ack 1
> jlaughlin@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
> jlaughlin@jlaughlin ~/Downloads/qpid-0.5/python/commands
> $ python2.5 qpid-route queue add santa-anna jlaughlin alarms alarmd --ack 1 --src-local
> jlaughlin@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
> jlaughlin@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:
> jlaughlin@jlaughlin ~/Downloads/qpid-0.5/python/commands
> $ python2.5 qpid-route queue add santa-anna jlaughlin alarms alarmd --ack 1
> jlaughlin@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:dev-subscribe@qpid.apache.org
[jira] Commented: (QPID-2199) Federation connections initiated from
windows brokers stuck in "connecting" state
Posted by "Steve Huston (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-2199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12860313#action_12860313 ]
Steve Huston commented on QPID-2199:
------------------------------------
Kerry, there's another jira around somewhere that suggests ways to replace the compiler-directed tss with a run-time directed mechanism. That would alleviate the DLL-loading problems. Driving it from that angle may be more efficient. For now, you could try using the compiler-directed TSS on Windows (there's a QPID_TSS or some such macro that does this) to see if that's going to solve the problem.
> 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, qpidbroker.exe running under cmd.exe, other tools running under cygwin
> Ubuntu Hardy, qpid 0.5 compiled from source with unused return value patches, host santa-anna
> Reporter: Jeff Laughlin
> Attachments: linux.cap, linux.out, windows.cap, windows.out
>
>
> 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
> jlaughlin@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
> jlaughlin@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.
> jlaughlin@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.
> jlaughlin@jlaughlin ~/Downloads/qpid-0.5/python/commands
> $ python2.5 qpid-route queue add scengsrv jlaughlin alarms alarmd --ack 1
> jlaughlin@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
> jlaughlin@jlaughlin ~/Downloads/qpid-0.5/python/commands
> $ python2.5 qpid-route queue add santa-anna jlaughlin alarms alarmd --ack 1 --src-local
> jlaughlin@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
> jlaughlin@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:
> jlaughlin@jlaughlin ~/Downloads/qpid-0.5/python/commands
> $ python2.5 qpid-route queue add santa-anna jlaughlin alarms alarmd --ack 1
> jlaughlin@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:dev-subscribe@qpid.apache.org
[jira] Commented: (QPID-2199) Federation connections initiated from
windows brokers stuck in "connecting" state
Posted by "Kerry Bonin (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-2199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12863497#action_12863497 ]
Kerry Bonin commented on QPID-2199:
-----------------------------------
I've modified the AsynchConnector class in the Windows AsynchIO.cpp code to perform asynchronous connects and the links are still reported stuck in connecting state. I'm now digging into how link state is managed after the connection succeeds.
> 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, qpidbroker.exe running under cmd.exe, other tools running under cygwin
> Ubuntu Hardy, qpid 0.5 compiled from source with unused return value patches, host santa-anna
> Reporter: Jeff Laughlin
> Attachments: linux.cap, linux.out, windows.cap, windows.out
>
>
> 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
> jlaughlin@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
> jlaughlin@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.
> jlaughlin@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.
> jlaughlin@jlaughlin ~/Downloads/qpid-0.5/python/commands
> $ python2.5 qpid-route queue add scengsrv jlaughlin alarms alarmd --ack 1
> jlaughlin@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
> jlaughlin@jlaughlin ~/Downloads/qpid-0.5/python/commands
> $ python2.5 qpid-route queue add santa-anna jlaughlin alarms alarmd --ack 1 --src-local
> jlaughlin@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
> jlaughlin@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:
> jlaughlin@jlaughlin ~/Downloads/qpid-0.5/python/commands
> $ python2.5 qpid-route queue add santa-anna jlaughlin alarms alarmd --ack 1
> jlaughlin@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:dev-subscribe@qpid.apache.org
[jira] Commented: (QPID-2199) Federation connections initiated from
windows brokers stuck in "connecting" state
Posted by "Ted Ross (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-2199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12777665#action_12777665 ]
Ted Ross commented on QPID-2199:
--------------------------------
It appears that the connection is being established but the notification to the LinkRegistry of the new connection never arrives. The AsynchIO::AsynchConnector is actually synchronous/blocking in the Windows implementation (it's asynchronous in the Linux implementation). It's possible that this is causing problems.
-Ted
> 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, qpidbroker.exe running under cmd.exe, other tools running under cygwin
> Ubuntu Hardy, qpid 0.5 compiled from source with unused return value patches, host santa-anna
> Reporter: Jeff Laughlin
> Attachments: linux.cap, linux.out, windows.cap, windows.out
>
>
> 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
> jlaughlin@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
> jlaughlin@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.
> jlaughlin@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.
> jlaughlin@jlaughlin ~/Downloads/qpid-0.5/python/commands
> $ python2.5 qpid-route queue add scengsrv jlaughlin alarms alarmd --ack 1
> jlaughlin@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
> jlaughlin@jlaughlin ~/Downloads/qpid-0.5/python/commands
> $ python2.5 qpid-route queue add santa-anna jlaughlin alarms alarmd --ack 1 --src-local
> jlaughlin@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
> jlaughlin@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:
> jlaughlin@jlaughlin ~/Downloads/qpid-0.5/python/commands
> $ python2.5 qpid-route queue add santa-anna jlaughlin alarms alarmd --ack 1
> jlaughlin@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:dev-subscribe@qpid.apache.org
[jira] Commented: (QPID-2199) Federation connections initiated from
windows brokers stuck in "connecting" state
Posted by "Jeff Laughlin (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-2199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12777637#action_12777637 ]
Jeff Laughlin commented on QPID-2199:
-------------------------------------
also interesting to note that on both ends, netstat reports an established connection
On windows;
jlaughlin@jlaughlin ~/Downloads/qpid-0.5/python/commands
$ netstat -an |grep 5672
TCP 0.0.0.0:5672 0.0.0.0:0 LISTENING
TCP 10.3.40.21:24601 10.3.40.21:5672 TIME_WAIT
TCP 10.3.40.21:24603 10.3.40.222:5672 ESTABLISHED
TCP 127.0.0.1:24606 127.0.0.1:5672 TIME_WAIT
On linux:
jlaughlin@santa-anna:~/qpid/qpid-0.5/python$ sudo netstat -anlp |grep qpid
tcp 0 0 0.0.0.0:5672 0.0.0.0:* LISTEN 3027/qpidd
tcp 0 0 10.3.40.222:5672 10.3.40.21:24603 ESTABLISHED 3027/qpidd
> 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
> Attachments: linux.out, windows.out
>
>
> 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
> jlaughlin@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
> jlaughlin@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.
> jlaughlin@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.
> jlaughlin@jlaughlin ~/Downloads/qpid-0.5/python/commands
> $ python2.5 qpid-route queue add scengsrv jlaughlin alarms alarmd --ack 1
> jlaughlin@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
> jlaughlin@jlaughlin ~/Downloads/qpid-0.5/python/commands
> $ python2.5 qpid-route queue add santa-anna jlaughlin alarms alarmd --ack 1 --src-local
> jlaughlin@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
> jlaughlin@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:
> jlaughlin@jlaughlin ~/Downloads/qpid-0.5/python/commands
> $ python2.5 qpid-route queue add santa-anna jlaughlin alarms alarmd --ack 1
> jlaughlin@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:dev-subscribe@qpid.apache.org
[jira] Commented: (QPID-2199) Federation connections initiated from
windows brokers stuck in "connecting" state
Posted by "Kerry Bonin (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-2199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12860270#action_12860270 ]
Kerry Bonin commented on QPID-2199:
-----------------------------------
I'm looking at ways to fix this...
The cleanest fix would appear to be to generalize the Posix version so it runs on Windows. The main problem I've seen so far with that approach is the Posix code uses thread local storage, which is unusable on Windows (if the code could run in a DLL loaded with LoadLibrary on OS's before Vista or Server 2008, see http://msdn2.microsoft.com/en-us/library/2s9wt68x.aspx for details.) Simplest way to address that would seem to add these variables to the AsynchIO class and lock before use. For now I'll copy the Posix version over the Windows version and see about making the changes there. Comments appreciated!
Kerry
> 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, qpidbroker.exe running under cmd.exe, other tools running under cygwin
> Ubuntu Hardy, qpid 0.5 compiled from source with unused return value patches, host santa-anna
> Reporter: Jeff Laughlin
> Attachments: linux.cap, linux.out, windows.cap, windows.out
>
>
> 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
> jlaughlin@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
> jlaughlin@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.
> jlaughlin@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.
> jlaughlin@jlaughlin ~/Downloads/qpid-0.5/python/commands
> $ python2.5 qpid-route queue add scengsrv jlaughlin alarms alarmd --ack 1
> jlaughlin@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
> jlaughlin@jlaughlin ~/Downloads/qpid-0.5/python/commands
> $ python2.5 qpid-route queue add santa-anna jlaughlin alarms alarmd --ack 1 --src-local
> jlaughlin@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
> jlaughlin@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:
> jlaughlin@jlaughlin ~/Downloads/qpid-0.5/python/commands
> $ python2.5 qpid-route queue add santa-anna jlaughlin alarms alarmd --ack 1
> jlaughlin@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:dev-subscribe@qpid.apache.org
[jira] Updated: (QPID-2199) Federation connections initiated from
windows brokers stuck in "connecting" state
Posted by "Jeff Laughlin (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-2199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jeff Laughlin updated QPID-2199:
--------------------------------
Attachment: windows.cap
linux.cap
Port 5672 packet logs from both machines
> 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, qpidbroker.exe running under cmd.exe, other tools running under cygwin
> Ubuntu Hardy, qpid 0.5 compiled from source with unused return value patches, host santa-anna
> Reporter: Jeff Laughlin
> Attachments: linux.cap, linux.out, windows.cap, windows.out
>
>
> 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
> jlaughlin@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
> jlaughlin@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.
> jlaughlin@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.
> jlaughlin@jlaughlin ~/Downloads/qpid-0.5/python/commands
> $ python2.5 qpid-route queue add scengsrv jlaughlin alarms alarmd --ack 1
> jlaughlin@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
> jlaughlin@jlaughlin ~/Downloads/qpid-0.5/python/commands
> $ python2.5 qpid-route queue add santa-anna jlaughlin alarms alarmd --ack 1 --src-local
> jlaughlin@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
> jlaughlin@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:
> jlaughlin@jlaughlin ~/Downloads/qpid-0.5/python/commands
> $ python2.5 qpid-route queue add santa-anna jlaughlin alarms alarmd --ack 1
> jlaughlin@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:dev-subscribe@qpid.apache.org
[jira] Updated: (QPID-2199) Federation connections initiated from
windows brokers stuck in "connecting" state
Posted by "Jeff Laughlin (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-2199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jeff Laughlin updated QPID-2199:
--------------------------------
Attachment: windows.out
I updated the windows.out log file to exclude the "link list" request that the previous one had included (which had doubled its size)
> 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, qpidbroker.exe running under cmd.exe, other tools running under cygwin
> Ubuntu Hardy, qpid 0.5 compiled from source with unused return value patches, host santa-anna
> Reporter: Jeff Laughlin
> Attachments: linux.out, windows.out
>
>
> 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
> jlaughlin@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
> jlaughlin@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.
> jlaughlin@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.
> jlaughlin@jlaughlin ~/Downloads/qpid-0.5/python/commands
> $ python2.5 qpid-route queue add scengsrv jlaughlin alarms alarmd --ack 1
> jlaughlin@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
> jlaughlin@jlaughlin ~/Downloads/qpid-0.5/python/commands
> $ python2.5 qpid-route queue add santa-anna jlaughlin alarms alarmd --ack 1 --src-local
> jlaughlin@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
> jlaughlin@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:
> jlaughlin@jlaughlin ~/Downloads/qpid-0.5/python/commands
> $ python2.5 qpid-route queue add santa-anna jlaughlin alarms alarmd --ack 1
> jlaughlin@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:dev-subscribe@qpid.apache.org
[jira] Commented: (QPID-2199) Federation connections initiated from
windows brokers stuck in "connecting" state
Posted by "Ted Ross (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-2199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12777591#action_12777591 ]
Ted Ross commented on QPID-2199:
--------------------------------
Jeff,
Can you get a trace from the Windows broker that is supposed to be initiating the connection? This should provide some clues. On Linux, this is done by using the "-t" command line option. I assume it's similar on Windows.
-Ted
> 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
> jlaughlin@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
> jlaughlin@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.
> jlaughlin@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.
> jlaughlin@jlaughlin ~/Downloads/qpid-0.5/python/commands
> $ python2.5 qpid-route queue add scengsrv jlaughlin alarms alarmd --ack 1
> jlaughlin@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
> jlaughlin@jlaughlin ~/Downloads/qpid-0.5/python/commands
> $ python2.5 qpid-route queue add santa-anna jlaughlin alarms alarmd --ack 1 --src-local
> jlaughlin@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
> jlaughlin@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:
> jlaughlin@jlaughlin ~/Downloads/qpid-0.5/python/commands
> $ python2.5 qpid-route queue add santa-anna jlaughlin alarms alarmd --ack 1
> jlaughlin@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:dev-subscribe@qpid.apache.org
[jira] Updated: (QPID-2199) Federation connections initiated from
windows brokers stuck in "connecting" state
Posted by "Jeff Laughlin (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-2199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jeff Laughlin updated QPID-2199:
--------------------------------
Environment:
Windows XP, qpid 0.5 from .msi installer, hosts scengsrv and jlaughlin, qpidbroker.exe running under cmd.exe, other tools running under cygwin
Ubuntu Hardy, qpid 0.5 compiled from source with unused return value patches, host santa-anna
was:
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
> 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, qpidbroker.exe running under cmd.exe, other tools running under cygwin
> Ubuntu Hardy, qpid 0.5 compiled from source with unused return value patches, host santa-anna
> Reporter: Jeff Laughlin
> Attachments: linux.out, windows.out
>
>
> 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
> jlaughlin@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
> jlaughlin@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.
> jlaughlin@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.
> jlaughlin@jlaughlin ~/Downloads/qpid-0.5/python/commands
> $ python2.5 qpid-route queue add scengsrv jlaughlin alarms alarmd --ack 1
> jlaughlin@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
> jlaughlin@jlaughlin ~/Downloads/qpid-0.5/python/commands
> $ python2.5 qpid-route queue add santa-anna jlaughlin alarms alarmd --ack 1 --src-local
> jlaughlin@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
> jlaughlin@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:
> jlaughlin@jlaughlin ~/Downloads/qpid-0.5/python/commands
> $ python2.5 qpid-route queue add santa-anna jlaughlin alarms alarmd --ack 1
> jlaughlin@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:dev-subscribe@qpid.apache.org
[jira] Updated: (QPID-2199) Federation connections initiated from
windows brokers stuck in "connecting" state
Posted by "Jeff Laughlin (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-2199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jeff Laughlin updated QPID-2199:
--------------------------------
Attachment: (was: windows.out)
> 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, qpidbroker.exe running under cmd.exe, other tools running under cygwin
> Ubuntu Hardy, qpid 0.5 compiled from source with unused return value patches, host santa-anna
> Reporter: Jeff Laughlin
> Attachments: linux.out, windows.out
>
>
> 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
> jlaughlin@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
> jlaughlin@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.
> jlaughlin@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.
> jlaughlin@jlaughlin ~/Downloads/qpid-0.5/python/commands
> $ python2.5 qpid-route queue add scengsrv jlaughlin alarms alarmd --ack 1
> jlaughlin@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
> jlaughlin@jlaughlin ~/Downloads/qpid-0.5/python/commands
> $ python2.5 qpid-route queue add santa-anna jlaughlin alarms alarmd --ack 1 --src-local
> jlaughlin@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
> jlaughlin@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:
> jlaughlin@jlaughlin ~/Downloads/qpid-0.5/python/commands
> $ python2.5 qpid-route queue add santa-anna jlaughlin alarms alarmd --ack 1
> jlaughlin@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:dev-subscribe@qpid.apache.org