| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Multiple errors |
« View previous topic :: View next topic » |
| Author |
Message
|
| wmqiadmin |
 Posted: Tue Mar 28, 2006 10:23 am Post subject: Multiple errors |
 |
|
Disciple
Joined: 19 Jun 2005
Posts: 163
Location: epping UK
|
Hi Guys,
I am facing multiple problems while processing my message flow. I am working with Broker, ConfigManager and toolkit V6 with fixpack 1 for toolkit on windows 2003, every thing on different m/c.
1. I am getting this errors from EVENT VIEWER on broker:
| Quote: |
| a. Error detected whilst processing a message in node 'EVENT_ROUTING_MF'.RouteToLable. Message broker detects an error whilst processing a msg in node 'EVENT_ROUTING_MF'.RouteToLable. |
Routing flow is working some time and doesn't work second time. Its behaviour is unpredectible. It send same message some time to the ouptput Q and to the failure Q some time. The compute mode has been set to all. Labels has been checked the ESQL is correct and Q names has been copied and pasted in the MQ nodes. I think there is no error in the flow.
| Quote: |
| b. Unable to locate lable node, A route to lable node has recieved a message containing a lable but there is no lable node with this label. |
The lable names has been checked and they are correct. I have created the appropriate output Queues.
| Quote: |
| c. Unable to open Q Route_Fail on MQ Q Mgr completion code 2, Reason code 2085. |
Q manager is running fine doesn't have any errors in the log file.
Main thing here is that, i have created this message flow multiple time and it works fine initially (for 2 lables) the message goes to the output Q through the routing and then when i add additional lables it start giving errors. Now its putting the message in a q which i am not using in this message flow(i used in previous message flow). The behaviour is not predictable some time it puts the message in the output Q and some time in the failure Q. To get the exact error i tried to get the exception list in a compute node before sending message to the failure output Q. broker doesn't read the compute node and sends the input message to the failure Q which should not happen, it should write the error details.
I thought the workspace is corrupted because it was not reading the ESQl yesterday and creating new ESQL every time when i give open ESQL cmd on compute node, so i created a new workspace, deleted the deployed message flows from the execution group and created new message flows deployed only single message flow on the execution group and still the problem is same.
Can any buddy please give me some idea what is happening and what to do to resolve this problem. |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Tue Mar 28, 2006 10:35 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Trace your flow using Trace nodes, writing to Files.
Watch what your flow does using the Debugger.
Make sure that every ESQL module you have that uses "PROPAGATE" either uses "PROPAGATE ... Delete NONE" or ends with "Return FALSE;".
Confirm that your ESLQ is not, for example, adding blank spaces to the front or end of your routing labels.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| wmqiadmin |
| Posted: Tue Mar 28, 2006 12:08 pm Post subject: |
|
|
Disciple
Joined: 19 Jun 2005
Posts: 163
Location: epping UK
|
I think I got the problem but i don't know how to resolve it.
When i try to open the debugger, in that it shows me my 3 execution groups with same name but different process id in Flow Engine. Can any buddy please tell me how to kill the multiple occurance of the same processes. |
|
| 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
|
|
|
|
