| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Need help understanding the error log |
« View previous topic :: View next topic » |
| Author |
Message
|
| Ravee Bhat |
 Posted: Wed Aug 27, 2008 10:56 am Post subject: Need help understanding the error log |
 |
|
Apprentice
Joined: 28 Apr 2004
Posts: 28
Location: Bangalore, INDIA
|
In the system the queue downstream was full and started refusing the incoming messages directed from the message flow on the broker.
In the exception log I found these lines,
| Code: |
/build/S500_P/src/DataFlowEngine/ImbMqInputNode.cpp:
3905: ImbMqInputNode::eligibleForBackout: ComIbmMQInputNode:
ACTUAL_MESSAGE_FLOW_NAME_HERE#FCMComposite_1_1 |
My query is,
0. whats the meaning of eligibleForBackout?
1. Can I almost be sure that this is the node where I can put a alternate flow for "failure" to be redirected to another queue/flow? (this is a MQInput node and does not have anything for either "Failure" or "Catch" )
Thanks in advance
Ravee
_________________
Lets go see The World. |
|
| Back to top |
|
 |
| broker_new |
| Posted: Wed Aug 27, 2008 6:14 pm Post subject: |
|
|
Yatiri
Joined: 30 Nov 2006
Posts: 614
Location: Washington DC
|
I have one doubt in your question....whether the catch terminal is wired in ur message flow or if it is wired is exception is not handled properly in error handler.if it is handled properly then there should be no question of backout...  |
|
| Back to top |
|
|
| Ravee Bhat |
| Posted: Wed Aug 27, 2008 9:52 pm Post subject: |
|
|
Apprentice
Joined: 28 Apr 2004
Posts: 28
Location: Bangalore, INDIA
|
Broker_New
There is no catch terminal wired in our case.
thanks
Ravee
_________________
Lets go see The World. |
|
| Back to top |
|
|
| sandeep9678 |
| Posted: Thu Aug 28, 2008 12:11 am Post subject: |
|
|
Apprentice
Joined: 04 Aug 2008
Posts: 41
Location: India
|
was your code running fine and then started giving error? Or right after deployment, flow is behaving like this?
_________________
Cheers,
Sandeep |
|
| Back to top |
|
|
| Ravee Bhat |
| Posted: Thu Aug 28, 2008 2:42 am Post subject: |
|
|
Apprentice
Joined: 28 Apr 2004
Posts: 28
Location: Bangalore, INDIA
|
yes, the message flow to send out the messages was working fine. No issues there. The transaction property on this node is Automatic.
A lil more investigation yielded in the information that when the queue downstream was full, the broker started putting them into undelivered.queue and when that became full, the message were sent to dead.queue. Now the dead.queue became full and thats when this exception was seen.
Looks like a bad design for message flows!!
But my query about how to read a log still there.
thanks
Ravee
_________________
Lets go see The World. |
|
| 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
|
|
|
|
