[
https://issues.apache.org/jira/browse/QPID-4664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13611278#comment-13611278
]
Chuck Rolke commented on QPID-4664:
-----------------------------------
You can actually get QPID wire tracing from your windows client code as a
built-in feature. Try:
SET QPID_LOG_ENABLE=trace+
run-application
For instance:
X:\>map_sender
X:\>map_receiver.exe
{colours:[red, green, white], id:987654321, name:Widget,
percent:0.98999999999999999, uuid:bc4c9003-a4e5-40d7-9f30-b44fc6f20154}
X:\>set QPID_LOG_ENABLE=trace+
X:\>map_sender
2013-03-22 17:19:26 debug Created connection amqp:tcp:127.0.0.1:5672 with {}
2013-03-22 17:19:26 info Trying to connect to amqp:tcp:127.0.0.1:5672...
2013-03-22 17:19:26 debug Created IO thread: 0
2013-03-22 17:19:26 debug TCPConnector created for 0-10
2013-03-22 17:19:26 debug RECV [[127.0.0.1:50289-127.0.0.1:5672]]: INIT(0-10)
2013-03-22 17:19:26 trace RECV [[127.0.0.1:50289-127.0.0.1:5672]]: Frame[BEbe;
channel=0; {ConnectionStartBody:
server-properties={qpid.federation_tag:V2:36:str16(acc48a25-758c-4939-9086-1c61824227f3)
}; mechanisms=str16{V2:9:str16(ANONYMOUS), V2:5:str16(PLAIN)};
locales=str16{V2:5:str16(en_US)}; }]
2013-03-22 17:19:26 debug WindowsSasl::start(ANONYMOUS PLAIN)
2013-03-22 17:19:26 trace SENT [[127.0.0.1:50289-127.0.0.1:5672]]: Frame[BEbe;
channel=0; {ConnectionStartOkBody:
client-properties={qpid.client_pid:F4:int32(3876),qpid.client_ppid:F4:int32(0),qpid.cl
ient_process:V2:0:str16(),qpid.session_flow:F4:int32(1)}; mechanism=PLAIN;
response=xxxxxx; locale=en_US; }]
2013-03-22 17:19:27 trace RECV [[127.0.0.1:50289-127.0.0.1:5672]]: Frame[BEbe;
channel=0; {ConnectionTuneBody: channel-max=32767; max-frame-size=65535;
heartbeat-min=0; heartbeat-max=0; }]
2013-03-22 17:19:27 trace SENT [[127.0.0.1:50289-127.0.0.1:5672]]: Frame[BEbe;
channel=0; {ConnectionTuneOkBody: channel-max=32767; max-frame-size=65535;
heartbeat=0; }]
2013-03-22 17:19:27 trace SENT [[127.0.0.1:50289-127.0.0.1:5672]]: Frame[BEbe;
channel=0; {ConnectionOpenBody: virtual-host=; capabilities=void{}; insist=1; }]
2013-03-22 17:19:27 trace RECV [[127.0.0.1:50289-127.0.0.1:5672]]: Frame[BEbe;
channel=0; {ConnectionOpenOkBody: known-hosts=str16{}; }]
2013-03-22 17:19:27 debug Known-brokers for connection:
2013-03-22 17:19:27 info Connection [127.0.0.1:50289-127.0.0.1:5672] connected
to tcp:127.0.0.1:5672
2013-03-22 17:19:27 debug Connection [127.0.0.1:50289-127.0.0.1:5672] no
security layer in place
2013-03-22 17:19:27 info Connected to amqp:tcp:127.0.0.1:5672
2013-03-22 17:19:27 debug Added known-hosts,
reconnect-urls=[amqp:tcp:127.0.0.1:5672]
2013-03-22 17:19:27 debug SessionState::SessionState .: 00D26F20
2013-03-22 17:19:27 trace SENT [[127.0.0.1:50289-127.0.0.1:5672]]: Frame[BEbe;
channel=1; {SessionAttachBody: name=7dc3bc7c-e626-4a6d-9d8b-1799ff7ec1b4; }]
2013-03-22 17:19:27 trace RECV [[127.0.0.1:50289-127.0.0.1:5672]]: Frame[BEbe;
channel=1; {SessionAttachedBody: name=7dc3bc7c-e626-4a6d-9d8b-1799ff7ec1b4; }]
2013-03-22 17:19:27 trace RECV [[127.0.0.1:50289-127.0.0.1:5672]]: Frame[BEbe;
channel=1; {SessionCommandPointBody: command-id=0; command-offset=0; }]
2013-03-22 17:19:27 trace SENT [[127.0.0.1:50289-127.0.0.1:5672]]: Frame[BEbe;
channel=1; {SessionRequestTimeoutBody: timeout=0; }]
2013-03-22 17:19:27 trace SENT [[127.0.0.1:50289-127.0.0.1:5672]]: Frame[BEbe;
channel=1; {SessionCommandPointBody: command-id=0; command-offset=0; }]
2013-03-22 17:19:27 trace SENT [[127.0.0.1:50289-127.0.0.1:5672]]: Frame[BEbe;
channel=1; {ExecutionSyncBody: }]
2013-03-22 17:19:27 trace RECV [[127.0.0.1:50289-127.0.0.1:5672]]: Frame[BEbe;
channel=1; {SessionTimeoutBody: timeout=0; }]
2013-03-22 17:19:27 trace RECV [[127.0.0.1:50289-127.0.0.1:5672]]: Frame[BEbe;
channel=1; {SessionCompletedBody: commands={ [0,0] }; }]
2013-03-22 17:19:27 trace SENT [[127.0.0.1:50289-127.0.0.1:5672]]: Frame[BEbe;
channel=1; {ExchangeBoundBody: exchange=message_queue; queue=message_queue;
binding-key=; arguments={}; }]
2013-03-22 17:19:27 trace RECV [[127.0.0.1:50289-127.0.0.1:5672]]: Frame[BEbe;
channel=1; {ExecutionResultBody: command-id=1; value=\x07\x02\x01\x00; }]
2013-03-22 17:19:27 trace RECV [[127.0.0.1:50289-127.0.0.1:5672]]: Frame[BEbe;
channel=1; {SessionCompletedBody: commands={ [0,1] }; }]
2013-03-22 17:19:28 debug treating target address as queue:
message_queue;{create:always}
2013-03-22 17:19:28 debug Auto-creating queue 'message_queue'
2013-03-22 17:19:28 trace SENT [[127.0.0.1:50289-127.0.0.1:5672]]: Frame[BEbe;
channel=1; {QueueDeclareBody: queue=message_queue; alternate-exchange=;
arguments={}; }]
2013-03-22 17:19:28 trace SENT [[127.0.0.1:50289-127.0.0.1:5672]]: Frame[BEbe;
channel=1; {ExecutionSyncBody: }]
2013-03-22 17:19:28 trace RECV [[127.0.0.1:50289-127.0.0.1:5672]]: Frame[BEbe;
channel=1; {SessionCompletedBody: commands={ [0,3] }; }]
2013-03-22 17:19:28 trace SENT [[127.0.0.1:50289-127.0.0.1:5672]]: Frame[Bbe;
channel=1; {MessageTransferBody: destination=; accept-mode=1; acquire-mode=0; }]
2013-03-22 17:19:28 trace SENT [[127.0.0.1:50289-127.0.0.1:5672]]: Frame[be;
channel=1; header (59 bytes); properties={{MessageProperties:
content-length=108; correlation-id=; content-type=amqp/map; u
ser-id=; application-headers={}; }{DeliveryProperties:
routing-key=message_queue; }}]
2013-03-22 17:19:28 trace SENT [[127.0.0.1:50289-127.0.0.1:5672]]: Frame[Ebe;
channel=1; content (108 bytes)
\x00\x00\x00h\x00\x00\x00\x05\x07colours\xA9\x00\x00\x00\x1A\x00\x00\x00\x03\x90\x00\x03red
\x90...]
2013-03-22 17:19:28 trace SENT [[127.0.0.1:50289-127.0.0.1:5672]]: Frame[BEbe;
channel=1; {ExecutionSyncBody: }]
2013-03-22 17:19:28 trace RECV [[127.0.0.1:50289-127.0.0.1:5672]]: Frame[BEbe;
channel=1; {SessionCompletedBody: commands={ [0,5] }; }]
2013-03-22 17:19:28 trace SENT [[127.0.0.1:50289-127.0.0.1:5672]]: Frame[BEbe;
channel=1; {SessionDetachBody: name=7dc3bc7c-e626-4a6d-9d8b-1799ff7ec1b4; }]
2013-03-22 17:19:28 trace RECV [[127.0.0.1:50289-127.0.0.1:5672]]: Frame[BEbe;
channel=1; {SessionDetachedBody: name=7dc3bc7c-e626-4a6d-9d8b-1799ff7ec1b4;
code=0; }]
2013-03-22 17:19:28 trace SENT [[127.0.0.1:50289-127.0.0.1:5672]]: Frame[BEbe;
channel=0; {ConnectionCloseBody: reply-code=200; reply-text=OK; }]
2013-03-22 17:19:28 trace RECV [[127.0.0.1:50289-127.0.0.1:5672]]: Frame[BEbe;
channel=0; {ConnectionCloseOkBody: }]
2013-03-22 17:19:28 debug Exception constructed: Closed by client
> 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]
