| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| delay in message being sent to client trigger monitor |
« View previous topic :: View next topic » |
| Author |
Message
|
| phawkins |
 Posted: Mon May 19, 2003 9:19 am Post subject: delay in message being sent to client trigger monitor |
 |
|
Newbie
Joined: 19 May 2003
Posts: 2
|
Just started using triggering and wondering if this situation is normal or not. The mqseries configuration I'm working in is MQ series server 5.3 (Win 2000) and a client (also win 2000). Triggering is set to first on the trigger queue. I start a client trigger monitor in a CMD window so I can watch the arrival of the trigger message. I then go to my mainframe which puts a message to the queue (using PUT1). My put message options are fail-if-quiescing, syncpoint, and new-msg-id. It takes betweeen 35 - 55 seconds for me to see the trigger message in the trigger monitor window. Is this normal?  |
|
| Back to top |
|
 |
| tillywern |
| Posted: Mon May 19, 2003 11:56 am Post subject: |
|
|
Centurion
Joined: 28 Jan 2003
Posts: 109
Location: Colorado
|
It is not normal for you to see this type of delay. I suspect that it may have something to do with how MQ commit points are being managed. Remember that a message may contribute to the depth of a queue while is still not committed. Until it is committed the receiving program can’t act upon it.
I can’t say that this is defiantly the case or not. I would try placing a message onto the Windows queue from the windows machine and see if you see the lag. If the lag disappears the problem would be in either how the data got into the mainframe queue or in how your channels are configured. If the lag remains then the problem is on the windows machine…
Hope this helps. |
|
| Back to top |
|
|
| alexsreis |
| Posted: Mon Sep 29, 2003 6:27 am Post subject: Confirm if MESSAGEID is been automatic generate (low value) |
|
|
Newbie
Joined: 26 Sep 2003
Posts: 1
|
Confirm if MESSAGEID is been generated (MQMI-NONE)
Confirme se o MessageId está sendo gerado automaticamente no COBOL isso é feito ajustando o MESSAGEID para MQMI-NONE. Caso este campo não esteja sendo constantemente setado, ele irá assumir o Identificado antigo e no momento da leitura o Listener pode entender que a mensagem já foi lida até expirar o tempo de cerca de 1 minuto. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Mon Sep 29, 2003 8:48 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
Message ID should have nothing to do with this.
whether a message is committed or not, it counts towards the depth of the queue and thus triggering. If all the other triggering conditions are there, than putting the message will immediatly cause the trigger, regardless of syncpoint. You triggered app then has to deal with the fact that there is an uncommitted message that is unavailable. Regardless, you would see the trigger message immediatly.
My guess is that one of the trigger conditions is not present at the time of the put. The most common mistake is that when you opened the queue to do the put, you may have specified the INPUT and OUTPUT option. If MQ sees that the queue is open for input, it assumes someone is getting from it, and so there is no trigger. When you close the queue from the put, MQ sees there is more than 0 messages on a triggered on first queue, and then it prodices the trigger message.
Check your MQOPEN options on the put. It should be OUTPUT only.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| 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
|
|
|
|
