Author |
Message
|
nathanw |
Posted: Tue May 17, 2005 8:18 am Post subject: WBI Bug problem? |
|
|
 Knight
Joined: 14 Jul 2004 Posts: 550
|
Hey all had a query from a client
Tell me what you think
----
The scenario is as follows:
1. We have a main flow that uses a subflow
2. The same subflow is used in lots of main flows, its purpose is to write
debug information to a trace file
3. The subflow contains a trace node with two promoted properties that
specify the filename to write to, and the contents of the trace (for
example the message root)
4. We start with everything running happily on the Broker
5. In the Message Broker Toolkit, we make a small change to the subflow -
for example, we slightly move the position of a node in the graphical view
of the flow. This change does not alter anything significant about the
flow, and it does not alter the functionality of the flow in any way.
6. The Message Broker Toolkit registers that a change has been made, so we
click on Save
7. If we then open up the main flow, the contents of the promoted
properties from the subflow have disappeared, although we have not touched
the main flow in any way.
My first question is, if the contents of the promoted properties are stored
against the main flow (I presume they are) then why should the contents be
cleared out if you change the subflow? We have not touched the promoted
properties at all.
So carrying on,
8. If you then deploy the main flow to the Broker, strangely enough
everything still works as normal
9. So we then make a similar minimal change to the main flow - we don't
touch the promoted properties at all - we then save the changes in Broker
Toolkit
10. We deploy the main flow to the Broker again. This time round, the
trace file will not be produced because the contents of the promoted
properties have disappeared from the Broker and it doesn't have a filename
to write to
This could cause us some problems in future if we need to alter one of
these subflows that have promoted properties. We can make changes in our
development procedures to get around the problem, but we would still like
an explanation because on the face of it, it appears to be a bug.
-------
So my next question is, do you consider this to be a bug?
Your thoughts |
|
Back to top |
|
 |
jefflowrey |
Posted: Tue May 17, 2005 8:20 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
I'd guess that saving the subflow causes it to be removed and readded to the main flow's node list.
Does this behavior change if you have subflows in separate projects? _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
nathanw |
Posted: Tue May 17, 2005 8:23 am Post subject: |
|
|
 Knight
Joined: 14 Jul 2004 Posts: 550
|
thx jeff my inital thoughts as well
they want to raise a PMR about this and have told them to make sure they have tested in throughly first
not sure about your question but i think yes
the subflows are used across multiple projects and execution groups
but surely when the message flow is compiled in the abr it should take all these into account. |
|
Back to top |
|
 |
jefflowrey |
Posted: Tue May 17, 2005 8:26 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
I guess my question was - does this happen if the subflow is in a different project, or does it "work" if it's in a different project.
It sounds like it is broken in either case - subflow in the same project, subflow in a different project.
When building the bar file - the properties should be visible to be overridden - but if the contents have been removed, then they've been removed. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
nathanw |
Posted: Tue May 17, 2005 8:41 am Post subject: |
|
|
 Knight
Joined: 14 Jul 2004 Posts: 550
|
I concur
Will discuss with them tomorrow |
|
Back to top |
|
 |
martinrydman |
Posted: Tue May 17, 2005 8:42 am Post subject: |
|
|
 Centurion
Joined: 30 Jan 2004 Posts: 139 Location: Gothenburg, Sweden
|
Just wanted to confirm this strange behaviour. I've run across it sporadically, but it never itched enough to fire the PMR gun
/Martin |
|
Back to top |
|
 |
nathanw |
Posted: Wed May 18, 2005 12:49 am Post subject: |
|
|
 Knight
Joined: 14 Jul 2004 Posts: 550
|
The problem is that the sub flows that, for want of a better word, error are used in multiple instances and the last thing the client wants s for a change to take place that will in effect remove any tracing etc as this in inherrant to the solution they have. |
|
Back to top |
|
 |
vmcgloin |
Posted: Wed May 18, 2005 3:08 am Post subject: |
|
|
Knight
Joined: 04 Apr 2002 Posts: 560 Location: Scotland
|
Hi,
It sounds like a bug to me and will affect a lot of our flows (in our case we have promoted properties from an Exception Handling subflow). Can you let us know how your pmr progresses if you raise one?
Cheers,
Vicky |
|
Back to top |
|
 |
nathanw |
Posted: Wed May 18, 2005 3:46 am Post subject: |
|
|
 Knight
Joined: 14 Jul 2004 Posts: 550
|
Strangely enough this is for error handling (or at least a major protion) aswell |
|
Back to top |
|
 |
Ian |
Posted: Wed May 18, 2005 5:18 am Post subject: |
|
|
Disciple
Joined: 22 Nov 2002 Posts: 152 Location: London, UK
|
Fixed under APAR IC41136 in WBIMB v5 FP4
The error description is that when promoting a mandatory property of a compute node to the subflow level, on each change of the subflow (even if the change is only to move the pisition of a node and save) then then promoted property value, which is set on the subflow node, is changed back to it's default value.
A possible workaround is to close the message flow editor on the main flow and re-open it. The ESQL module property should have retrieved its good value. _________________ Regards, Ian |
|
Back to top |
|
 |
nathanw |
Posted: Wed May 18, 2005 5:30 am Post subject: |
|
|
 Knight
Joined: 14 Jul 2004 Posts: 550
|
Ian
I was wondering how long it would take a hursley person to answer.
Many thanks
So if the close the editor and reopen it before they compile the bar file it should re promote the values.
I will inform and let you know. |
|
Back to top |
|
 |
|