| Author |
Message
|
| Inforz |
 Posted: Thu Jan 17, 2013 10:26 am Post subject: msg going to DLQ |
 |
|
Centurion
Joined: 15 Apr 2011
Posts: 139
Location: Chennai, India
|
I tried to drop a msg from QM1's remote q(Q1) to QM2's local q(Q2). when dropped it goes to DLQ of QM2. but when dropped using amqsput the msg is delivered correctly to Q2. Sender@QM1 and Receiver at QM2 are created as required.
What would be the prob?
P.S. This question might be common, but pls bear with me, its urgent |
|
| Back to top |
|
 |
| Vitor |
| Posted: Thu Jan 17, 2013 10:29 am Post subject: Re: msg going to DLQ |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Inforz wrote: |
| What would be the prob? |
It's the problem described by the reason code in a DLH.
| Inforz wrote: |
| P.S. This question might be common, but pls bear with me, its urgent |
Then you should ask it elsewhere. This is not a help desk with an SLA on replies; you could be stuck for hours or days waiting.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Inforz |
| Posted: Thu Jan 17, 2013 10:34 am Post subject: |
|
|
Centurion
Joined: 15 Apr 2011
Posts: 139
Location: Chennai, India
|
| the DLQ header shows "invalid object/object not found". but as I said when dropped in amqsput it goes without any hurdles to the q. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Jan 17, 2013 10:48 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
So you have APP1 that sends a message to a qremote.
You have APP2 that is actually amqsput that sends a message to a qremote.
APP1's message does not get delivered.
APP2's message does get delivered.
The fault is in APP1. |
|
| Back to top |
|
|
| Inforz |
| Posted: Fri Jan 18, 2013 5:12 am Post subject: |
|
|
Centurion
Joined: 15 Apr 2011
Posts: 139
Location: Chennai, India
|
just to be clear
when msg is dropped form QM1's RQ, the msg goes to DLQ of QM2
but when dropped from amqsput sample of QM2's server, the msg is delivered correctly
Also the destination q in QM2 is a cluster queue(and its visible to other cluster QMs) and transactions within the server's QM and that queue is perfectly fine |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Fri Jan 18, 2013 6:21 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
Use amqsput on QM1 to put to that RQ.
You will likely find this goes to the DLQ as well.
You will likely find the remote queue definition on QM1 is not properly defined given the rest of your MQ topology.
You may also find other MQ defintions that are incorrect.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Fri Jan 18, 2013 7:49 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9470
Location: US: west coast, almost. Otherwise, enroute.
|
| Inforz wrote: |
just to be clear
when msg is dropped form QM1's RQ, the msg goes to DLQ of QM2 |
This implies a badly created QRemote definition.
| Inforz wrote: |
| but when dropped from amqsput sample of QM2's server, the msg is delivered correctly |
This implies that the destination queue on QM2 exists.
| Inforz wrote: |
| Also the destination q in QM2 is a cluster queue (and its visible to other cluster QMs) and transactions within the server's QM and that queue is perfectly fine |
If the destination queue is a cluster queue, and QM1 is in the cluster, why do you use a QRemote definition on QM1? Delete the QRemote definition on QM1, and let clustering software find the destination queue in its usual way.
_________________
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 |
|
|
|
|
