| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| 2189 and retry |
« View previous topic :: View next topic » |
| Author |
Message
|
| mqbee |
 Posted: Thu Nov 04, 2010 4:37 am Post subject: 2189 and retry |
 |
|
Novice
Joined: 31 Jul 2003
Posts: 15
|
Hi All,
I have messages in DLQ for the reason 2189 (MQRC_CLUSTER_RESOLUTION_ERROR) pertaining to some time frame when there was a cluster issue. Now that is solved I want to replay these messages. I had following entries in my DLH rules table, but thats not working,
REASON(MQRC_CLUSTER_RESOLUTION_ERROR) ACTION(FWD) FWDQ(&DESTQ)
and tried this one as well,
REASON(MQRC_CLUSTER_RESOLUTION_ERROR) ACTION(RETRY)
am I missing anything?
Thanks in advance,
mqbee. |
|
| Back to top |
|
 |
| Mr Butcher |
| Posted: Thu Nov 04, 2010 5:00 am Post subject: |
|
|
Padawan
Joined: 23 May 2005
Posts: 1716
|
are you sure that queue is available again? try to open it using amqsput.
are there more than one qmgr on that machine? if so, did runmqdlq pick the correct one?
any messages from runmqdlq?
i would go for the retry statement, but it looks good for me.
_________________
Regards, Butcher |
|
| Back to top |
|
|
| shashivarungupta |
| Posted: Thu Nov 04, 2010 7:39 am Post subject: Re: 2189 and retry |
|
|
Grand Master
Joined: 24 Feb 2009
Posts: 1343
Location: Floating in space on a round rock.
|
| mqbee wrote: |
I have messages in DLQ for the reason 2189 (MQRC_CLUSTER_RESOLUTION_ERROR) pertaining to some time frame when there was a cluster issue. Now that is solved I want to replay these messages. I had following entries in my DLH rules table, but thats not working,
REASON(MQRC_CLUSTER_RESOLUTION_ERROR) ACTION(FWD) FWDQ(&DESTQ)
and tried this one as well,
REASON(MQRC_CLUSTER_RESOLUTION_ERROR) ACTION(RETRY) |
On which O.S. you are doing it ?
WHEN CREATING THE RULES TABLE., TO INSTRUCT DEAD LETTER QUEUE HANDLER TO PROCESS THE MESSAGES...'MAKE SURE THERE IS A BLANK LINE AT THE END OF THE RULES TABLE. The blank line as the last line is a requirement for MQ on Windows only.'
*Just wanting to remind you that runmqdlq is a server process and cannot use a client connection.
..WHEN RUNNING THE RUNMQDLQ COMMAND WITHOUT PARAMETERS (NO Q NAME , NO QM NAME) NEITHER THESE ARE MENTIONED IN RULES TABLE THEN YOU'LL GET " Unable to connect to queue manager. " CONNECTION ERROR.
By the way you can find lots of Posts related to this topic here.
_________________
*Life will beat you down, you need to decide to fight back or leave it. |
|
| Back to top |
|
|
| mqbee |
| Posted: Sun Nov 07, 2010 6:49 pm Post subject: |
|
|
Novice
Joined: 31 Jul 2003
Posts: 15
|
Mr Butcher wrote:
| Quote: |
are you sure that queue is available again? try to open it using amqsput.
are there more than one qmgr on that machine? if so, did runmqdlq pick the correct one?
any messages from runmqdlq?
|
Queue is available as there is no more exception once the cluster issue is resolved.
Only one qmgr, again, I have provided the qmgr name inside the DLH file for the parameter inputqm.
No message from runmqdlq
shashivarungupta wrote:
| Quote: |
On which O.S. you are doing it ?
|
AIX, still I have provided a blank line in the end, no joy 
Thanks,
mqbee. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sun Nov 07, 2010 10:19 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Does the qmgr name in the DLH handler rule (1st line or cmd line parm) match the qmgr name on the box?
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| mqbee |
| Posted: Thu Nov 18, 2010 9:42 pm Post subject: |
|
|
Novice
Joined: 31 Jul 2003
Posts: 15
|
| Yes, qmgr name matches... all other rules in the rule table are working except for this... |
|
| Back to top |
|
|
| Mr Butcher |
| Posted: Thu Nov 18, 2010 11:52 pm Post subject: |
|
|
Padawan
Joined: 23 May 2005
Posts: 1716
|
| Quote: |
| Queue is available as there is no more exception once the cluster issue is resolved. |
how did you verify it? on the queuemanager you try to retry the messages from the DLQ, try an amqsput to that queue (of course without puttins someting). and check if the mqopen works. also use a display qcluster. also use a display clusqmgr / display cluster channels to make sure you are properly in contact with the cluster. verify queuemanager and queue name of the messages in the dlq if that really matches what you think it should. after you run the dlq handler, is the returncode still 2189, or did it change?
one more thing... the retry of the dlqhandler ... i am not sure how the mqopen is performed. with queue name only, or with queue name and qmgr name. imho, it must be performed with queue and qmgr name , otherwise a message hitting the DLQ failing because remote queuemanager is unknown would (or could) be delivered to a queue local to the queuemanager the dlq handler runs on on the retry command, if the dlq handler does not take the queuemanager into account on the mqopen.
but this may not be what you want in terms of your cluster, as messages have been put to cluster queue name only. so on the original put the queuename counts for cluster resolution, and now, on the retry, it is the qmgr name that is used ?!? (well, if a queuemanagername has been assigned ever. but its you that can check the DLQ header).
so maybe it is worth using a forward with header no and fwdq = cluster queue name instead of the retry ..... to have mq run through the cluster name resolution again by queue name only .....
_________________
Regards, Butcher |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Fri Nov 19, 2010 6:25 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
WHEN CREATING THE RULES TABLE., TO INSTRUCT DEAD LETTER QUEUE HANDLER TO PROCESS THE MESSAGES...'MAKE SURE THERE IS A BLANK LINE AT THE END OF THE RULES TABLE. The blank line as the last line is a requirement for MQ on Windows only.'
*Just wanting to remind you that runmqdlq is a server process and cannot use a client connection.
..WHEN RUNNING THE RUNMQDLQ COMMAND WITHOUT PARAMETERS (NO Q NAME , NO QM NAME) NEITHER THESE ARE MENTIONED IN RULES TABLE THEN YOU'LL GET " Unable to connect to queue manager. " CONNECTION ERROR.
Orange color makes it even harder to read, and less likely that anyone will reply.
_________________
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 |
|
|
|
|
|
| |
|
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
|
|
|
|
