[
https://issues.apache.org/jira/browse/QPID-4664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13612749#comment-13612749
]
Steve Huston commented on QPID-4664:
------------------------------------
Wireshark won't be able to tell you the _content_ of the frames if SSL is used,
but it would be helpful to correlate if the events you see in "trace+" logging
are actually happening on the wire.
> 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]
