| Author |
Message
|
| gregbui |
 Posted: Thu Feb 19, 2004 7:25 pm Post subject: RouteToLabel DISASTER!!!! |
 |
|
Newbie
Joined: 02 Feb 2004
Posts: 2
|
Hey all,
I have been beating my head on this problem for a while now and was wondering if anyone could shed some light on this issue. Basically I'm using a DestinationList and RouteToLabel nodes in my flow, but it seems to die as it hits one of the RouteToLabel nodes. I have TRIPLE checked labels to ensure they are correct and QUADRUPLE checked the destination list creation logic to ensure it is correct. Everything appears just fine but I continue to receive the following errors:
UserTrace BIP4160I: Message propagated to match terminal by check node 'UEP_Main_Flow_FEB16.FlowOrder1'. The check node 'UEP_Main_Flow_FEB16.FlowOrder1' has matched a received message against the criteria and is propagating it to any nodes connected to its match terminal. No user action required.
2621 Error BIP2628E: Exception condition detected on input node 'UEP_Main_Flow_FEB16.UEI.COSAUTO.IN'. The input node 'UEP_Main_Flow_FEB16.UEI.COSAUTO.IN' detected an error whilst processing a message. The message flow has been rolled-back and, if the message was being processed in a unit of work, it will remain on the input queue to be processed again. Following messages will indicate the cause of this exception. Check the error messages which follow to determine why the exception was generated, and take action as described by those messages.
2621 RecoverableException BIP2230E: Error detected whilst processing a message in node 'UEP_Main_Flow_FEB16.RouteToLabel7'. The message broker detected an error whilst processing a message in node 'UEP_Main_Flow_FEB16.RouteToLabel7'. An exception has been thrown to cut short the processing of the message.
See the following messages for details of the error.
2621 RecoverableException BIP4240E: RouteToLabel node 'UEP_Main_Flow_FEB16.RouteToLabel7' unable to locate Label node ''. A RouteToLabel node has received a message containing a label but there is no Label node with this label. This problem may result from the logic of the message flow as specified by the user not calculating a valid Label node name for all valid input messages, from the input message being of an unexpected nature or from the deployed configuration not being as intended. Check the logic of the message flow to ensure that in all cases the calculated Label node names will be correct and then check that the input message is not of an unexpected nature. Finally ensure that the message flow, and any nested message flows have been checked in. Redeploy the new configuration to the broker ensuring that the complete configuration option is used. If the problem persists, contact your IBM support center.
Any help on this pain in my arse would be greatly appreciated!!
Deeply DISTRESSED,
Greg |
|
| Back to top |
|
 |
| Missam |
| Posted: Thu Feb 19, 2004 8:01 pm Post subject: |
|
|
Chevalier
Joined: 16 Oct 2003
Posts: 424
|
Hi
Don't get DISTRESSED.First tell which version of MQSI and CSD's are you working on.Can you post your flow here.
The Error About RouteToLabel is Specific and it's saying you doesn't have Matching Label Nodes how did u specify your DestinationList there.
Its sholud be some thing like this
SET OutputLocalEnvironment.Destination.RouterList.DestinationData[1].labelName = 'xyz'
and you should have LabelNode with the same name.Check Once again |
|
| Back to top |
|
|
| mqsidude |
| Posted: Thu Feb 19, 2004 8:06 pm Post subject: |
|
|
Centurion
Joined: 22 Jan 2004
Posts: 148
|
Hey greg,
Did you check the 'Compute Mode' property of the compute node where you are building the destination list? It should be set to either 'LocalEnvironment and Message' or 'All'.
'Ideally set it to ALL'.
Hope this helps! |
|
| Back to top |
|
|
| mqsidude |
| Posted: Thu Feb 19, 2004 8:37 pm Post subject: |
|
|
Centurion
Joined: 22 Jan 2004
Posts: 148
|
| mqsidude wrote: |
Hey greg,
Did you check the 'Compute Mode' property of the compute node where you are building the destination list? It should be set to either 'LocalEnvironment and Message' or 'All'.
Ideally set it to 'ALL'.
Hope this helps!
|
|
|
| Back to top |
|
|
| sido |
| Posted: Thu Feb 19, 2004 9:44 pm Post subject: Destination List |
|
|
Novice
Joined: 02 Feb 2004
Posts: 23
|
I work with greg. The answer to the questions are:
MQSI version 2.1 and CSD version 4.
Yes, all the nodes are set to i) LocalEnvironment and Message OR ii)All.
As for the labels, the Label Name in the DestinationList MATCHES the Label Names on the Label Nodes. This has been verified by 3 people.
The logic for our flow is that we have different labels for different functionality. Some labels are mandatorily traversed - others are traversed depending on conditional logic. |
|
| Back to top |
|
|
| kirani |
| Posted: Thu Feb 19, 2004 11:29 pm Post subject: Re: Destination List |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
| sido wrote: |
| Some labels are mandatorily traversed - others are traversed depending on conditional logic. |
Are you sure that your condition is met in this case? Try printing the LocalEnvironment tree in a trace node and see the label is getting set.
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
| Michael Dag |
| Posted: Fri Feb 20, 2004 12:54 am Post subject: |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)
|
may sound stupid, but HOW did you verify the label names...
did you check the label name in the properties window?
I have wrecked my brain once, copied a label node, renamed it, but
never looked at the label name... 
Michael |
|
| Back to top |
|
|
| gregbui |
| Posted: Fri Feb 20, 2004 7:10 am Post subject: |
|
|
Newbie
Joined: 02 Feb 2004
Posts: 2
|
hehe - I guess distressed is too strong a word 
Thanks Sido for answering those questions. You're such a hottie... 
Ok, on to the questions...
Kirani - Yes, we are quite sure that the destination list is constructed correctly. We sprinkled trace nodes throughout the flow to capture environemnt, destlist and message information. The destlist is created with the appropriate labels for the message type and, if you review the last error message, there is no reference to an empty(' ') label.
MichaelDag - yes, I have checked, double checked and triple checked the label names to ensure they are correct. My initial thought was that a label was missing, however it could not be so easy!
mqsidude - yes, all compute nodes that update environment variable data are set to ALL.
If anyone has additional thoughts your help would be appreciated.
Regards,
Greg |
|
| Back to top |
|
|
| EddieA |
| Posted: Fri Feb 20, 2004 8:54 am Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
| Quote: |
| Yes, all the nodes are set to i) LocalEnvironment and Message OR ii)All. |
In every one of these nodes are you transferring the InputLocalEnvironment to OutputLocalEnvironment.
This is only moved automatically when you DON'T have it specified in the Advanced Properties.
| Quote: |
| We sprinkled trace nodes throughout the flow to capture environemnt |
The best place would be immediately before the RouteToLabel.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| catwood2 |
| Posted: Tue Mar 09, 2004 3:29 pm Post subject: |
|
|
Centurion
Joined: 17 May 2002
Posts: 108
|
Greg -
Ever get this sorted out? I am on 2.1 csd6 and experiencing the identical problem. I have output the local environment to trace file (trace node just before RouteToLabel) and the tree looks correct. I know the label exists and is correct. I'll post when I figure it out. Or, better yet, you've figured it out and could share.
thx |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Mar 09, 2004 3:58 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| catwood2 wrote: |
| I am on 2.1 csd6 and experiencing the identical problem. I have output the local environment to trace file (trace node just before RouteToLabel) and the tree looks correct. |
Post it, and we'll double-check your work. Never hurts to have another set of  eyes to look at it..
Also, are you trying to route to a Label that is in a subflow? You can't do that.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| catwood2 |
| Posted: Wed Mar 10, 2004 9:10 am Post subject: |
|
|
Centurion
Joined: 17 May 2002
Posts: 108
|
Thanks Jeff.
As I was double checking my config this morning, using this thread as a guide, turns out that my setting of the DestinationList didn't match the second post by IamSam:
| Code: |
| SET OutputLocalEnvironment.Destination.RouterList.DestinationData[1].labelName = 'xyz' |
I had a variation that was populating the DestinationList in Trace - but apparently lacking something critical (will go read up on that).
I actually am routing to a label in a subflow successfully in this flow (2.1csd6). Not sure if that conflicts with your statement.
thx again |
|
| Back to top |
|
|
| EddieA |
| Posted: Wed Mar 10, 2004 9:22 am Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
| Quote: |
| I actually am routing to a label in a subflow successfully in this flow (2.1csd6). Not sure if that conflicts with your statement. |
I think Jeff was alluding to the Route to Label node being in the main flow, but the actual Label node is inside a Subflow.
If both the Route to and the Label nodes are in the same flow, main, or sub, then all is OK.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Mar 10, 2004 9:23 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
To the best of my knowledge, you can't use a RouteToLabel node in the main flow to route to a Label node in a subflow.
But you can use a RouteToLabel node within a subflow to route to a Label node within the subflow.
But maybe they've changed this in CSD6 for 2.1, and it may (probably) have different behavior in v5.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
|
|
