| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| amqsput 2053 but no SDLQ |
« View previous topic :: View next topic » |
| Author |
Message
|
| ivanachukapawn |
 Posted: Thu Jul 29, 2010 5:05 am Post subject: amqsput 2053 but no SDLQ |
 |
|
Knight
Joined: 27 Oct 2003
Posts: 561
|
I ran amqsput on a queue which had depth at the MAX and received a 2053. My intention was to run some tests on runmqdlq. However, after receiving the 2053 the SDLQ had a queue depth of 0.
Peter said in an earlier post:
Here are some of the more common reasons for messages ending up in a DLQ:
MQRC_PUT_INHIBITED
(2051, X'803') Put calls inhibited for the queue.
MQRC_Q_FULL
(2053, X'805') Queue already contains maximum number of messages.
Any theory on why I can get a message into the SDLQ? |
|
| Back to top |
|
 |
| bruce2359 |
| Posted: Thu Jul 29, 2010 5:09 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
The queue is local to the application - same o/s image - no network. If the queue is local, the app receives ReasonCode QUEUE_FULL, and no attempt is made to use the dlq.
_________________
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 |
|
|
| ivanachukapawn |
| Posted: Thu Jul 29, 2010 5:12 am Post subject: |
|
|
Knight
Joined: 27 Oct 2003
Posts: 561
|
| Thanks Bruce for that information. If I go ahead and put messages directly to SDLQ do you think that my tests on runmqdlq will work (I guess they would be missing the dlq header)? |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Thu Jul 29, 2010 5:27 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
No, no. Application should NOT put messages directly on the DLQ!
The purpose of the system DLQ is for the qmgr to put messages when the downstream (down the network) queue is not available.
One of the appropriate application-level recovery techniques: your application should catch the QUEUE_FULL condition, then open an application-specific dead letter queue (not the system dlq), an put the message there.
_________________
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 |
|
|
| ivanachukapawn |
| Posted: Thu Jul 29, 2010 5:37 am Post subject: |
|
|
Knight
Joined: 27 Oct 2003
Posts: 561
|
| Thanks for the insight. No problem. I'll just define a RQ to a non-existent LQ downstream and put to that. I'm just trying to run some tests on the runmqdlq utility. Much thanks. |
|
| Back to top |
|
|
| shashivarungupta |
| Posted: Thu Jul 29, 2010 6:11 am Post subject: |
|
|
Grand Master
Joined: 24 Feb 2009
Posts: 1343
Location: Floating in space on a round rock.
|
| ivanachukapawn wrote: |
| I'll just define a RQ to a non-existent LQ downstream and put to that. |
Another scenario for queue full i.e. 2053 would be define QRD and point it to the Local Queue which would be remote to the local qmgr and set max depth to 1 and try putting message couple of times to test your scenarios.
_________________
*Life will beat you down, you need to decide to fight back or leave it. |
|
| 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
|
|
|
|
