|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
messages in fail queue!!!!! |
« View previous topic :: View next topic » |
Author |
Message
|
cute_pav |
Posted: Tue Apr 15, 2003 2:08 pm Post subject: messages in fail queue!!!!! |
|
|
Acolyte
Joined: 04 Jan 2002 Posts: 65 Location: usa
|
I have strange situation to deal with and need some help.
In our environment message are often going to message flow fail queues that provided in flow design.
But those flows are successfully tested and ran through the flow in earlier.When I tried complete deployment on Broker they are working fine.
I am guessing this is some thing to do with system environment respective to WMQI.
Can anyone face this issue earlier!!!! appreciate your valuable suggestions and experience.
pavan |
|
Back to top |
|
 |
lillo |
Posted: Tue Apr 15, 2003 11:49 pm Post subject: |
|
|
Master
Joined: 11 Sep 2001 Posts: 224
|
Could you give us a little more information, as a trace when the message goes to your failure queue? Explain the point where your message flow fails, ... _________________ Lillo
IBM Certified Specialist - WebSphere MQ |
|
Back to top |
|
 |
cute_pav |
Posted: Mon Apr 28, 2003 11:50 am Post subject: |
|
|
Acolyte
Joined: 04 Jan 2002 Posts: 65 Location: usa
|
Hi,
I don't have trace node for this message flow and it happens rarely in TEST machine while runtime.When I redeploy broker and run the same file, this feed going through proper queues without problem.I can't leave trace open as its heavier load on machine.
Ofcourse its strange problem but happenning several times in my broker.
I am sure this is not a problem with messageflow design as it works in usual case and may be relates to some environmental issues with broker and related stuff like.
Anyone has ideas in this regard!!!!!
pavan |
|
Back to top |
|
 |
jefflowrey |
Posted: Tue Apr 29, 2003 5:23 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
If you are not capturing, through a trace node or other means, any information about what the error is that is causing your messages to get sent to your failure queue, how do you expect to find out what the problem is?
Without any sorts of tracing, you can check your system log for error messages.
Otherwise, you can enable user tracing on the broker or message flow (without using trace nodes, mind you) to get a better idea of where your message flow is failing. See the Administration Guide's description of the 'mqsichangetrace' command for more information. |
|
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
|
|
|
|