| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Trigger type of first 'correct' for channel init? |
« View previous topic :: View next topic » |
| Author |
Message
|
| PisgahMan |
 Posted: Thu Feb 09, 2006 7:52 am Post subject: Trigger type of first 'correct' for channel init? |
 |
|
Voyager
Joined: 27 Jul 2004
Posts: 93
|
We saw a situation where a remote queue manager went down and messages built up on the local XMIT queue. I assumed that when the remote QM came back up the messages would drain but they did not.
I assume this is because the trigtype is first and my understanding from the admin guide is that is only triggered when the depth goes from 0 to 1.
A steady stream of over 1 million messages a day(really in an 8 hour period) pass thru this queue, so
setting it to trigger on any/every message doesn't really make sense(I don't think)
Is this a case where you would just restart and/or reset the channels on each end, or I am making some incorrect assumptions about trigtype?
Thanks |
|
| Back to top |
|
 |
| mvic |
| Posted: Thu Feb 09, 2006 7:57 am Post subject: Re: Trigger type of first 'correct' for channel init? |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
Is it possible to just leave your channels up and running all day? (Channel retry logic should then take care of outages like this). It sounds like you have the throughput to justify this approach...  |
|
| Back to top |
|
|
| KramJ |
| Posted: Thu Feb 09, 2006 8:23 am Post subject: |
|
|
Voyager
Joined: 09 Jan 2006
Posts: 80
Location: Atlanta
|
| You could toggle the trigger on the triggered queue. Set the queue to NOTRIGGER and then back to TRIGGER and it will start triggering. |
|
| Back to top |
|
|
| wschutz |
| Posted: Thu Feb 09, 2006 11:34 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
| Quote: |
I assume this is because the trigtype is first and my understanding from the admin guide is that is only triggered when the depth goes from 0 to 1.
|
No, thats not true. A trigger event will occur at qmgr startup when the channel initiation (runmqchi) starts and opens the initiation queue. When that happens, the qmgr goes around and looks at all the queues that name the initation as their INITQ, and creates a trigger message for that queue (provided it would normally meet the trigger condition). So, for example, all queues that have messages on them and TRIGTYPE=FIRST would cause a trigger message to be generated.
Of course, there's also TRIGMPRI, which says "don't count messages with a priority less than this. So, if you have a queue with 100 messages, all with priorty=3 and if the TRIGMPRI=5, then no trigger message would get generated. 
_________________
-wayne |
|
| Back to top |
|
|
| EddieA |
| Posted: Thu Feb 09, 2006 12:49 pm Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
| Quote: |
| I assume this is because the trigtype is first and my understanding from the admin guide is that is only triggered when the depth goes from 0 to 1. |
You can also get a trigger when the TRIGINT interval expires. But the default value for that is around 11 1/2 days.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| 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
|
|
|
|
