Posted: Sun Aug 08, 2010 9:29 pm Post subject: TimerNode ID
Jedi Council
Joined: 10 Feb 2003 Posts: 6076 Location: Somewhere over the Rainbow this side of Never-never land.
In the docs, is specifies that A TimeoutNode must have a unique ID on a per broker basis. (6.1.0.5, windows)
Accidentally, I deployed two flows to the same broker, same EG with the same timer node id.
I know that they were the same as both flows embedded the same subflow that contained the TimeoutNode.
Both timers worked perfectly.
So I did a test.
I deployed one flow with the timer set to 600secs. Then I deployed the other flow this time I set it to 900secs.
24hours later, both timers are working fine.
My questions is,
Are the docs wrong or was I lucky that it all worked? Our prod brokers are on Solaris so I want to ask this before I deploy to them (dev env).
It would be really nice to be able to be able to use subflows that contain TimeoutNodes as well as input & output Nodes. _________________ WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions.
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