| Author |
Message
|
| rdubey |
 Posted: Tue Feb 13, 2007 8:26 am Post subject: messages wont go from cluster transmit queue |
 |
|
Novice
Joined: 11 Jul 2006
Posts: 17
Location: USA
|
I had a problem with a qmgr on HP box and had to run the refresh cluster but after running refresh cluster i noticed messages not going from cluster command queue so i decided to cold start the queue manger .
i copied the messages from transmit queue using q program ( q -iQ1 -oQ2 ) and then i emptied the transmit queue, repository queue and command queue and stopped receiver channel and restarted the queue manager and then channels .every thing was looking fine and cluster was looking in good health so i copied the messages back to transmit queue but they still wont go while new messages are processing fine from transmit queue.
does anyone know if i used the correct option with q program to copy the message and that does not touch the header or message. |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Tue Feb 13, 2007 8:32 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Did you confirm that the messages were destined for a valid queue manager?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| rdubey |
| Posted: Tue Feb 13, 2007 2:33 pm Post subject: |
|
|
Novice
Joined: 11 Jul 2006
Posts: 17
Location: USA
|
| it looks like we found the problem . these messages are reply messages and go to the same qmanager who sent the request . it appears that during maintenence window the request message was sent by the queue manager which is only up during mainetence window and the messages were processed late when the maintenence window was over so that qmanager went down and other queue managers came up but reply messages are waiting on transmit queue since that queue manager is not up. |
|
| Back to top |
|
|
| Nigelg |
| Posted: Wed Feb 14, 2007 1:59 am Post subject: |
|
|
Grand Master
Joined: 02 Aug 2004
Posts: 1046
|
| Quote: |
.. refresh cluster
.. cold start the queue manager
.. emptied the transmit queue, repository queue and command queue
|
Wow, you certainly hit the panic button on his one. None of those operations have the slightest effect on the reported problem.
Looks like you suffer from management syllogism syndrome
We must do something..
This is something..
Let's do this!
Next time, try DISPLAY CHSTATUS, or DIS CLUSQMGR to check whether any channels are in RETRYING. Also, browse the cluster xmitq to check where the msgs are destined - the channel name is in the CorrelId field of the msg.
_________________
MQSeries.net helps those who help themselves.. |
|
| Back to top |
|
|
| rdubey |
| Posted: Thu Feb 15, 2007 7:46 am Post subject: |
|
|
Novice
Joined: 11 Jul 2006
Posts: 17
Location: USA
|
| how the channel name goes in correl id ? does sending app need to set an option somewhere ? is it documented somewhere ? |
|
| Back to top |
|
|
| HubertKleinmanns |
| Posted: Thu Feb 15, 2007 8:06 am Post subject: |
|
|
Shaman
Joined: 24 Feb 2004
Posts: 732
Location: Germany
|
| rdubey wrote: |
| how the channel name goes in correl id ? does sending app need to set an option somewhere ? is it documented somewhere ? |
The QMgr does - how ever should a cluster channel find its messages?
_________________
Regards
Hubert |
|
| Back to top |
|
|
| Nigelg |
| Posted: Fri Feb 16, 2007 1:21 am Post subject: |
|
|
Grand Master
Joined: 02 Aug 2004
Posts: 1046
|
It is not documeted that the channel name is in the CorrelId, but it is 'well-known'.
_________________
MQSeries.net helps those who help themselves.. |
|
| Back to top |
|
|
|
|
