| Author |
Message
|
| hari_92 |
 Posted: Mon Mar 09, 2015 12:36 am Post subject: How to store/view the messages received by MQ explorer? |
 |
|
Newbie
Joined: 09 Mar 2015
Posts: 2
|
I am using MQ explorer to connect a remote MQ manager. I want to view the messages received by the queue before it gets erased.
The queue processes the request message very quickly that the message is not displayed in the 'Browse Messages' window and I am not able to view the message. Is there a way to view all messages received by a queue? |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Mon Mar 09, 2015 4:27 am Post subject: Re: How to store/view the messages received by MQ explorer? |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20767
Location: LI,NY
|
| hari_92 wrote: |
I am using MQ explorer to connect a remote MQ manager. I want to view the messages received by the queue before it gets erased.
The queue processes the request message very quickly that the message is not displayed in the 'Browse Messages' window and I am not able to view the message. Is there a way to view all messages received by a queue? |
Have you thought about checking the processing application's logs? 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| zpat |
| Posted: Mon Mar 09, 2015 4:49 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5867
Location: UK
|
In a word, No.
However you can use pub/sub with a topic alias to duplicate messages.
Or just stop the application to allow inspection of the messages.
_________________
Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error. |
|
| Back to top |
|
|
| tczielke |
| Posted: Mon Mar 09, 2015 12:26 pm Post subject: |
|
|
Guardian
Joined: 08 Jul 2010
Posts: 942
Location: Illinois, USA
|
On distributed platforms, tracing does allow you to record the entire message body of GETs/PUTs for a running application. You can use either strmqtrc (with the -d option) or the Application Activity Trace ( configured through the mqat.ini file). You need to be 7.1 or higher to use the AAT.
_________________
Working with MQ since 2010. |
|
| Back to top |
|
|
| zpat |
| Posted: Tue Mar 10, 2015 12:23 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5867
Location: UK
|
Using tracing may affect performance, so be careful on production systems.
_________________
Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error. |
|
| Back to top |
|
|
| tczielke |
| Posted: Tue Mar 10, 2015 4:52 am Post subject: |
|
|
Guardian
Joined: 08 Jul 2010
Posts: 942
Location: Illinois, USA
|
| zpat wrote: |
| Using tracing may affect performance, so be careful on production systems. |
Yes, you definitely need to take that into consideration when using tracing. Here are a few tips for helping to mitigate some of the concerns with tracing (strmqtrc):
1) Use the -l option to put a limit on the file space. For example, strmqtrc -l 5 will only allow the trace file to grow to 5 Mb. You will have two files per process (.TRC for the active one and .TRS for the previous one).
2) Use the -p option to only trace the programs that you care about. For example, strmqtrc -p prog1 will only trace prog1. Based on some performance tests I have done, running with just strmqtrc -p prog1 only added less than milliseconds to the performance of the API calls for prog1.
The Activity Trace would have some overhead, as well. I have never seen any specifics on that documented. The Activity Trace is much more user friendly than strmqtrc, too.
_________________
Working with MQ since 2010. |
|
| Back to top |
|
|
|
|
