| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Trigger monitor dying after sometime |
« View previous topic :: View next topic » |
| Author |
Message
|
| Vin |
 Posted: Wed Sep 11, 2002 11:02 am Post subject: Trigger monitor dying after sometime |
 |
|
Master
Joined: 25 Mar 2002
Posts: 212
Location: India
|
| I'm running two trigger monitors against different queues. My platform is Solaris 2.8 running MQSeries 5.2. Initially both the trigger monitors run fine. After sometime one of them dies. It's always the same trigger monitor which is dying. I looked at the error logs and there was not FDC file for this. Does anyone know if this is a limitation on Solaris or is it something wrong which I'm doing? Thanks all. |
|
| Back to top |
|
 |
| bduncan |
| Posted: Wed Sep 11, 2002 3:22 pm Post subject: |
|
|
Padawan
Joined: 11 Apr 2001
Posts: 1554
Location: Silicon Valley
|
Trigger monitors are precarious beasts sometimes. I know the feeling of them dying without any apparent reason! I've found that one of the most useful methods for debugging this is to run the trigger monitor (runmqtrm) in the foreground and either sit there and watch it (if it dies right away) or pipe the stdout to a file which you can study later. The trigger monitor outputs quite a bit of information to stdout which you never see if you run it in the background (as people typically do).
_________________
Brandon Duncan
IBM Certified MQSeries Specialist
MQSeries.net forum moderator |
|
| Back to top |
|
|
| Vin |
| Posted: Wed Sep 11, 2002 3:56 pm Post subject: |
|
|
Master
Joined: 25 Mar 2002
Posts: 212
Location: India
|
| Thanks brandon. It's very weird. I did pipe the output to a file and nothing shows up there. It's not that the queue is getting triggered all the time. At some point of time this trigger monitor dies and there is no error generated. Really donno how to debug this? Thanks for the input. |
|
| Back to top |
|
|
| bduncan |
| Posted: Wed Sep 11, 2002 9:12 pm Post subject: |
|
|
Padawan
Joined: 11 Apr 2001
Posts: 1554
Location: Silicon Valley
|
But when the trigger DOES occur, you do see something in the output right? Hmm, this is interesting. The only other thing I can think of is to run a trace program in the hopes that the trigger monitor dies while it is running, and then you can at least look at the state of the shared memory, semaphores, etc...
The final alternative is to write you own trigger monitor, one which you can add lots and lots of logging to 
_________________
Brandon Duncan
IBM Certified MQSeries Specialist
MQSeries.net forum moderator |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
