can't see MQ purepath on WAS which is connected using MQ with Message Broker
There is no MQ purepath on WAS server which should be connected to ESB(Message broker) using message queue
From thread dump on WAS, can see threads calling MQ
If stop WAS server, can see the queue depth for esb.sip.req.cq2 is 12 which means the messages are accumulated in the queue then the other end stops responding
mqm@tuixpsp1[/var/mqm]# echo "dis q(esb.sip.req.cq2) curdepth" | runmqsc SIP.QM1 5724-H72 (C) Copyright IBM Corp. 1994, 2009. ALL RIGHTS RESERVED. Starting MQSC for queue manager SIP.QM1.
1 : dis q(esb.sip.req.cq2) curdepth AMQ8409: Display Queue details. QUEUE(ESB.SIP.REQ.CQ2) TYPE(QLOCAL) CURDEPTH(12)
|
When the was server starts, queue depth becomes 0 immediately
mqm@tuixpsp1[/var/mqm]# echo "dis q(esb.sip.req.cq2) curdepth" | runmqsc SIP.QM1 5724-H72 (C) Copyright IBM Corp. 1994, 2009. ALL RIGHTS RESERVED. Starting MQSC for queue manager SIP.QM1.
1 : dis q(esb.sip.req.cq2) curdepth AMQ8409: Display Queue details. QUEUE(ESB.SIP.REQ.CQ2) TYPE(QLOCAL) CURDEPTH(0) One MQSC command read. No commands have a syntax error. All valid MQSC commands were processed. |
From MB purepath, can see the message are sending to the queue “esb.sip.req.cq2” and “ESB.SIP.RES.LQ1”
Message queue sensor on WAS server(SIP) is enabled as “active and start purepath”
is there anything else i need to configure?
attached is the session files
Hello
The attached session file is not a session but a screenshot, so we can't have a closer look. From the screenshots, everything looks quite good actually. I can only speculate, but it may help to change the MQ correlation settings in "Server Settings -> MQ Tagging", i.e. enable queue name or queue manager correlation by checking the checkboxes.
Regards,
Markus
