| Author |
Message
|
| rammer |
 Posted: Wed Apr 11, 2012 4:51 pm Post subject: DLQ Conditions |
 |
|
Partisan
Joined: 02 May 2002
Posts: 359
Location: England
|
Evening.
Quick question on a recent observation.
Environment uses MQ Clustering. All messages go via a Gateway (MQ HUB) let call it QMGRHUB and are destined for QMGRA.
MQHUb is version 7.0.1.4
QMGRA is version 6.0.2.3
Both running on AIX
Queue A on QMGRA is the destination queue with max depth setting of 100000. Occasionally the receiving App fails so we hit maximum queue depth.
Only around 500 messages ever then spill onto QMGRA DLQ, the rest then get stuck on the SYSTEM.CLUSTER.TRANSMIT.QUEUE with the channel to QMGRA going into status of Stalled until we start to clear down the messages on 7.0.1.4
I thought that if Queue A became full, then messages would go to the DLQ until that became full or we ran out of disk space which ever occurred first! neither of these scenarios occur.
This is the only errors seen on the QMGRA
04/11/12 19:39:03 - Process(655452.210745) User(mqm) Program(amqrmppa)
AMQ9544: Messages not put to destination queue.
EXPLANATION:
During the processing of channel 'TO_QMDTSPRD' one or more messages could not
be put to the destination queue and attempts were made to put them to a
dead-letter queue. The location of the queue is 1, where 1 is the local
dead-letter queue and 2 is the remote dead-letter queue.
ACTION:
Examine the contents of the dead-letter queue. Each message is contained in a
structure that describes why the message was put to the queue, and to where it
was originally addressed. Also look at previous error messages to see if the
attempt to put messages to a dead-letter queue failed. The program identifier
(PID) of the processing program was '655452'.
Similar error on MQHUB
Thanks in advance. |
|
| Back to top |
|
 |
| bruce2359 |
| Posted: Wed Apr 11, 2012 5:02 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Are you running WMQ FTE?
_________________
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 |
|
|
| rammer |
| Posted: Wed Apr 11, 2012 5:05 pm Post subject: |
|
|
Partisan
Joined: 02 May 2002
Posts: 359
Location: England
|
| Hi, No not running WMQ FTE, this is just a standard MQ Cluster. Thanks |
|
| Back to top |
|
|
| rammer |
| Posted: Wed Apr 11, 2012 5:09 pm Post subject: |
|
|
Partisan
Joined: 02 May 2002
Posts: 359
Location: England
|
| One thing I forgot to add is that this Queue Manager QMGRA was rebuilt back in 2007, and looking at it there must have been some process's or something left lying around. The reason for this under /var/mqm/qmgr/ the queue manager directory is QMGRA.000, and there is still a QMGRA directory under there. Unsure if this is not helping the situation.. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Apr 11, 2012 7:33 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
And what is the max depth of the DLQ on qmgr A?
Also remember that cluster channel attributes can force the number of retries and the time between retries... 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| rammer |
| Posted: Wed Apr 11, 2012 7:41 pm Post subject: |
|
|
Partisan
Joined: 02 May 2002
Posts: 359
Location: England
|
DLQ limit is 999999999
Yep I understand the retires etc, but it doesnt explain why messages are not ALL put direct to the dlq? instead of just a few then putting the channel into SUSPEND does it? Maybe im going mad... |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Thu Apr 12, 2012 5:26 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
Stalled and Suspend are not MQ Channel Statuses. I think you mean Paused?
The receiving channel's Message Retry Interval and Message Retry Count attributes come into play when the channel can't put all the messages into the destination q because it is full.
Now that the destination q is full, your messages are slowly spilling over to the DLQ. If you wait long enough, and the destination queue remains full and itself is not draining, your cluster transmit q will eventually drain, and the DLQ depth will rise.
If your destination queue is slowly being processed, it may look like its full and not changing, but what's happening is as soon as there is room the channel fills it up again the next Message Retry Interval, and while the destination q is full, the channel throws additional messages to the DLQ.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| rammer |
| Posted: Thu Apr 12, 2012 6:10 am Post subject: |
|
|
Partisan
Joined: 02 May 2002
Posts: 359
Location: England
|
Apologise for incorrect grammar used, I blame jet-lag flying over from UK to USA the day before and having to start working at 1am  .
Anyway thanks for the response. I will monitor the situation when it next occurs which I am sure it will do soon.
Thanks. |
|
| Back to top |
|
|
|
|
