| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| MQ v6.0.2 and MQ Triggering |
« View previous topic :: View next topic » |
| Author |
Message
|
| Bni |
 Posted: Thu Apr 10, 2008 9:06 am Post subject: |
 |
|
Apprentice
Joined: 09 Aug 2006
Posts: 29
|
| Thank you very much for the kind replies. What I will do is to save all the pending messages in the queue before SAP is brought back up and then I will reenable the trigger. Depending on how many message I have in the queue at the time, I will set it to "first " or "every", in order to avoid a crush like suggested here. I think the messages will not pass 300 in the queue, the worst I can do is just to toggle the trigger on and off to process one message at the time and bring down the total number of waiting messages in the queue and then I will use trigger "every" when at a reasonable number of messages. Now I know this is a not a trigger issue but an application issue. |
|
| Back to top |
|
 |
| bruce2359 |
| Posted: Thu Apr 10, 2008 9:22 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9472
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| Depending on how many message I have in the queue at the time, I will set it to "first " or "every", in order to avoid a crush like suggested here. |
Which TRIGTYPE setting you pick should be based on what the MQGETting application does.
Find the programmer, and ask. Best practice is for the program to get-and-process messages until the queue is empty. This avoids having the consuming application re-launched for each message.
If the program is written to get one message, then end itself, find the programmer, and smack him/her with something.
In any case, leave TRIGTYPE(FIRST) untouched. Alter the TRIGGER attribute to turn triggering on/off.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| Bni |
| Posted: Thu Apr 10, 2008 10:56 am Post subject: |
|
|
Apprentice
Joined: 09 Aug 2006
Posts: 29
|
| Even if I want to, I could not, because people who wrote those programs were long gone and right now really not whole lot of people know those programs. looks like that I have to flip the trigger switch on and off to process those queued messages. That is sweet!!!!! Thanks folks, I learnt a lot from you guys. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Thu Apr 10, 2008 11:43 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9472
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| ...not whole lot of people know those programs |
This might be an opportunity for you to become familiar with WMQ programming concepts.
It helps if admins understand what programmers do; it helps if programmers understand what admins do.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Thu Apr 10, 2008 11:52 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
| Bni wrote: |
| then I will use trigger "every" when at a reasonable number of messages. Now I know this is a not a trigger issue but an application issue. |
Every is the worst choice if the app doesn't read till 2033. It WILL, guaranteed, leave a rolling backlog of messages sooner or later. With First the trigger will refire every time the app closes the q after getting one message so it will clean itself up by rapidly retriggering. There is the overhead of the rapid retriggers, but its better than stranded messages, no?
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
|
|
|
|
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
|
|
|
|
