Author |
Message
|
gyadavil |
Posted: Thu May 05, 2005 12:56 pm Post subject: I need help with Missing Messages |
|
|
Acolyte
Joined: 01 Feb 2005 Posts: 62
|
Hi
I am troubleshooting a problem with missing messages in WBIM5.0
I have a try catch node attached to the catch terminal of input node. Failure queue attached to the failure terminal of the input node. Out terminal of input node connected to a compute node. I know there is a problem with the esql code written in compute node. I used wrong Message Type name when I assign the text to OutputRoot.MRM
Message is unable to go to output node as the logical tree mismatch error occured. Then message is coming back all the way to Input node and then getting disappeared.
Persistence and synchpoint both set for Message. Input queue is persistent. Transaction mode in input node is Yes.
message is not going anywhere in the system.
Can someone help me out with this. |
|
Back to top |
|
 |
TonyD |
Posted: Thu May 05, 2005 3:07 pm Post subject: |
|
|
Knight
Joined: 15 May 2001 Posts: 540 Location: New Zealand
|
Have you looked in the DLQ? |
|
Back to top |
|
 |
gyadavil |
Posted: Thu May 05, 2005 8:38 pm Post subject: |
|
|
Acolyte
Joined: 01 Feb 2005 Posts: 62
|
Yes. But not there. Even in system broker queues, but could not find them.
I know the bug in the code and where it is erroring out. But as per my understanding it should endup in some queue rather than discarded..am I right ? |
|
Back to top |
|
 |
eknathv |
Posted: Thu May 05, 2005 11:12 pm Post subject: |
|
|
Apprentice
Joined: 14 Aug 2002 Posts: 27 Location: Bangalore
|
Hi,
Enable Tracing on the message flow & use mqsireadlog & mqsiformat log commands.
Tese commands will generate the log file which has complete out put. Where it will prompt where the message is going .
Good Luck. _________________ Eknath Vashishtha |
|
Back to top |
|
 |
waugh |
Posted: Fri May 06, 2005 5:42 am Post subject: |
|
|
 Master
Joined: 19 Feb 2004 Posts: 225
|
gyadavil,
disconnect any terminals connecting to failure queues. now only out terminals are connected. run your message again, it shud end up on input queue(coz theres an error in code), now connect each failure terminals one by one to see where exactly its going? |
|
Back to top |
|
 |
EddieA |
Posted: Fri May 06, 2005 10:48 am Post subject: |
|
|
 Jedi
Joined: 28 Jun 2001 Posts: 2453 Location: Los Angeles
|
Quote: |
But as per my understanding it should endup in some queue rather than discarded..am I right |
Not always. If you have a Filter Node, and the message takes one of the terminals, other than Error, that isn't connected to anything, then Poof, the message has travelled to the Big Bit Bucket in the Sky.
Cheers, _________________ Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
Back to top |
|
 |
gyadavil |
Posted: Fri May 06, 2005 10:56 am Post subject: |
|
|
Acolyte
Joined: 01 Feb 2005 Posts: 62
|
actually now I tested by removing the try catch node and then it ended up in failure queue. Strange.
Earlier, I can see in the flow debug the message coming back all the way to input node and also trying to reach try catch node then coming back.........then gone. I thought it will go to Failure queue connected to input node. That's what I thought when transactioin mode is set to Yes. |
|
Back to top |
|
 |
jefflowrey |
Posted: Fri May 06, 2005 11:00 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
Did you have anything connected to the Catch terminal?
If not, that's why. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
|