[
https://issues.apache.org/jira/browse/QPID-4664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13611170#comment-13611170
]
Steve Huston commented on QPID-4664:
------------------------------------
There is a possible bug which may be affecting this at
https://issues.apache.org/jira/browse/QPID-3759. Other than that, there aren't
any known problems. Note, though, that 0.14 is fairly old and many things have
been fixed since then. What version is running on Linux?
If you could reproduce this with a more up to date version it would be very
helpful.
Modern wireshark versions can parse AMQP 0-10, so you can use that to capture
traffic to help diagnose.
> Receiver fetching delays and Wire Captures for Qpid 0.14
> --------------------------------------------------------
>
> Key: QPID-4664
> URL: https://issues.apache.org/jira/browse/QPID-4664
> Project: Qpid
> Issue Type: Bug
> Components: C++ Client
> Affects Versions: 0.14
> Environment: Client is Windows C++ running on Windows Server 2008 (me)
> Server is Red Hat MRG (broker)
> Reporter: Jin-Ghee Lu
>
> My Windows C++ client (located in US) was seeing some issues while fetching
> messages from a broker (located in Europe). Sometimes the fetch call (with 1
> second timeout) will stuck there and not return, even after timeout
> supposedly elapsed; sometimes it would keep timing out if follow-up fetches
> were issued. Do anyone know if this is a known issue in 0.14, especially on
> Windows?
> Also, I would like to investigate on the wire if my sender actually sent
> something, or if there were messages coming into my network, just for some
> reasons, my fetch call didn't respond. How can I do a wire capture with
> Wireshark or something?
> Thanks.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
