| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| BIP4050E |
« View previous topic :: View next topic » |
| Author |
Message
|
| kirani |
 Posted: Fri Feb 01, 2002 1:30 pm Post subject: |
 |
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
Hi,
I have a main message flow (F1) and two subflows (sub1 and sub2).
In sub1 and sub2, based on some condition I am branching to different paths using Route to Label nodes.
Can I have same 'label name' in Label nodes, which are in different subflows?
For example,
In sub1, my 'Label Name' in different label nodes are 1, 2, 3, 4,5 and 6.
In sub2, my 'Label Name' in different label nodes are 1, 2, 3, 4,5 and 6.
I am getting an error during depoly time. The error is,
BIP4050E: Duplicate Label Name attribute '6' in Label node.
Two Label nodes within a message flow have been found to have the same Label Name attribute 6.
The message flow must be changed so that each Label node has a unique Label Name attribute.
I tried removing one of the subflow and the deploy was successful.
Am I missing something?
Kiran
|
|
| Back to top |
|
 |
| kirani |
| Posted: Fri Feb 01, 2002 3:03 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
I changed my 'Label Names' in both the sub-flow and it deployed successfully. Now my label names are distinct across flows,
Sub1: R1, R2, R3, R4, R5 and R6
Sub2: L1, L2, L3, L4, L5 and L6
Kiran
|
|
| Back to top |
|
|
| el_pollo_del_mar |
| Posted: Tue Oct 08, 2002 4:30 pm Post subject: BIP4050E thrown on all labelnames. |
|
|
Novice
Joined: 01 Jul 2002
Posts: 13
|
I'm having the same problem, except that no matter what I change the label name to the broker always throws a BIP4050E and states that the new labelname is a duplicate.
If I delete that label node, the error will occur with another, different label node. Even if I change -that- labelname, the BIP4050E still occurs.
I should also add that this problem is now occuring in message flows which were previously okay. Every single label in all message flows across my broker are unique, but BIP4050E's are still being thrown.
Any suggestions as to the cause? |
|
| Back to top |
|
|
| lung |
| Posted: Tue Oct 08, 2002 6:24 pm Post subject: |
|
|
Master
Joined: 27 Aug 2002
Posts: 291
Location: Malaysia
|
I suppose node names in different subflows can be the same, but if you decide to use multiple subflows together, then the node names in those subflows must be different than one another. So I think it's best to use different names for the nodes in all your subflows.
el_pollo_del_mar, I can think of no other cause other than maybe u missed out a node with the same name in your message flows. 
_________________
lung |
|
| Back to top |
|
|
| el_pollo_del_mar |
| Posted: Tue Oct 08, 2002 6:35 pm Post subject: |
|
|
Novice
Joined: 01 Jul 2002
Posts: 13
|
Unfortunately, that's not it. Like I said, changing the labelname will still throw a 'Duplicate LabelName Attribute' error: even if you change the labelname to something unlikely, eg, 'WEWXXDS'!
I've also tried deleting the broker, config manager and Databases, and recreating them. The error still occurs. |
|
| Back to top |
|
|
| el_pollo_del_mar |
| Posted: Tue Oct 08, 2002 9:01 pm Post subject: |
|
|
Novice
Joined: 01 Jul 2002
Posts: 13
|
Ok, after much trial and error, I've figured out what I did wrong on this one.
It's much the same problem as the original one described by Kirani, with a subtle difference: the preceeding message flow referenced my sub-flow (the flow in which the label conflict occured) twice. IE, instead of having two outputs to the one instance of the subflow, I had two outputs each going to its own instance of the subflow.
IE, I had:
1 ----- Subflow
2 ----- Subflow
Instead of:
1-----
|------- Subflow
2-----
For some reason, the broker must then treat this situation as having two identical subflows with the same names, attributes, etc. with errors resulting.
Is this expected behaviour from the broker? I wouldn't have thought so, but I have been proven wrong on issues like this often enough in the past. |
|
| Back to top |
|
|
| Yanghui |
| Posted: Wed Jun 11, 2003 1:28 am Post subject: |
|
|
Disciple
Joined: 08 May 2002
Posts: 151
Location: Dublin, Ireland
|
I am experiencing same problem right now. I am using WMQI2.1+CSD2. Does anybody know if the problem has been solved in the latest CSD or there is any work-around method?
It's quite easy to recreate the problem. If you have a subflow (named as SF) with RouteToLabel and some Label nodes in it, use a main flow to call this subflow twice, which means you have two subflow nodes SF1 and SF2 in the main flow. When you deploy it, you will get error BIP4050E to complain Duplicate labelName.
I think it's a very stupid mistake since subflow should have a isolated environment. The result should be only determined by passing in data not by the existence of other subflows or its other instance.
Thanks
-Yanghui |
|
| Back to top |
|
|
| kirani |
| Posted: Wed Jun 11, 2003 9:51 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
well .. sub-flow is like a macro, whose code gets inserted into main message flow when it gets deployed to the broker. So in this case, it will give an error if more than one label node is found with the same Label name.
_________________
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 |
|
|
|
|
|
| |
|
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
|
|
|
|
