ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » floeorder node

Post new topic  Reply to topic
 floeorder node « View previous topic :: View next topic » 
Author Message
rajendraprasad
PostPosted: Mon Jan 14, 2013 12:57 am    Post subject: floeorder node Reply with quote

Newbie

Joined: 14 Jan 2013
Posts: 3

if floworder node second out terminal process the message,then that processing fails then wat happened?pls help me
Back to top
View user's profile Send private message
sumit
PostPosted: Mon Jan 14, 2013 1:23 am    Post subject: Reply with quote

Partisan

Joined: 19 Jan 2006
Posts: 398

What is your scenario? What problem are you facing.
If processing fails at any node, the outcome depends how you are handling the exceptions and how is your flow configured (transaction mode, etc)
_________________
Regards
Sumit
Back to top
View user's profile Send private message Yahoo Messenger
lancelotlinc
PostPosted: Mon Jan 14, 2013 5:55 am    Post subject: Reply with quote

Jedi Knight

Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA

The first branch will have completed successfully but the second branch will have failed. If you intend to have all or nothing, then you will have to compensate the first branch.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER
Back to top
View user's profile Send private message Send e-mail
mgk
PostPosted: Mon Jan 14, 2013 7:12 am    Post subject: Reply with quote

Padawan

Joined: 31 Jul 2003
Posts: 1642

Quote:
The first branch will have completed successfully but the second branch will have failed


Actually both branches are under the same transaction, so if the exception thrown down branch 2 reaches the Input node, then any transactions down branch one will be rolled back.

Kind regards,
_________________
MGK
The postings I make on this site are my own and don't necessarily represent IBM's positions, strategies or opinions.
Back to top
View user's profile Send private message
kash3338
PostPosted: Mon Jan 14, 2013 9:20 am    Post subject: Reply with quote

Shaman

Joined: 08 Feb 2009
Posts: 709
Location: Chennai, India

lancelotlinc wrote:
The first branch will have completed successfully but the second branch will have failed.


This totally depends on the transactionality of the first branch. We can have both ways possible by our design.
Back to top
View user's profile Send private message Send e-mail
Vitor
PostPosted: Mon Jan 14, 2013 9:37 am    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

kash3338 wrote:
lancelotlinc wrote:
The first branch will have completed successfully but the second branch will have failed.


This totally depends on the transactionality of the first branch. We can have both ways possible by our design.


Give details, with especial reference to how you've moved the branches into 2 different units of work.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
kash3338
PostPosted: Mon Jan 14, 2013 9:47 am    Post subject: Reply with quote

Shaman

Joined: 08 Feb 2009
Posts: 709
Location: Chennai, India

Vitor wrote:

Give details, with especial reference to how you've moved the branches into 2 different units of work.


Say I have a Compute Node and a MQOutput node in both my branches and I set the transactionality to 'No' in my MQOutput in first branch. Then, even if there is a error during the processing in the second branch, my first branches message will be put in the MQ Queue.

If you want the entire transaction to roll back in case of failure in the second branch, set the Transactionality to 'Yes' so that nothing commits in the first branch.

Right?
Back to top
View user's profile Send private message Send e-mail
Vitor
PostPosted: Mon Jan 14, 2013 10:11 am    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

kash3338 wrote:
Vitor wrote:

Give details, with especial reference to how you've moved the branches into 2 different units of work.


Say I have a Compute Node and a MQOutput node in both my branches and I set the transactionality to 'No' in my MQOutput in first branch. Then, even if there is a error during the processing in the second branch, my first branches message will be put in the MQ Queue.

If you want the entire transaction to roll back in case of failure in the second branch, set the Transactionality to 'Yes' so that nothing commits in the first branch.

Right?


Suppose the first branch updates a database. What then?
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
lancelotlinc
PostPosted: Mon Jan 14, 2013 10:35 am    Post subject: Reply with quote

Jedi Knight

Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA

Also, some flows, we don't want to set Transaction to yes: for example, an MQ request/reply pattern.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER
Back to top
View user's profile Send private message Send e-mail
kash3338
PostPosted: Mon Jan 14, 2013 6:17 pm    Post subject: Reply with quote

Shaman

Joined: 08 Feb 2009
Posts: 709
Location: Chennai, India

Vitor wrote:
Suppose the first branch updates a database. What then?


Even then there is a option to 'Commit' the DB processing after the execution comes out of the Compute Node in the first path.

lancelotlinc wrote:

Also, some flows, we don't want to set Transaction to yes: for example, an MQ request/reply pattern.


Yes. I agree on this. Thats why I mentioned,

Quote:
We can have both ways possible by our design.


Based on our requirement/design we can make the first path to be commited/failed when there is some failure in the second path.
Back to top
View user's profile Send private message Send e-mail
smdavies99
PostPosted: Mon Jan 14, 2013 7:51 pm    Post subject: Reply with quote

Jedi Council

Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.

lancelotlinc wrote:
Also, some flows, we don't want to set Transaction to yes: for example, an MQ request/reply pattern.


I can add to that the output to logging queues in a flow where you are logging the inputs. You want to log the input even if later on there is an exception and everything rolls back. If the MQOutput i transactional you lose the input logs which if your error handling system is properly joined up with your logging system, you can connect the Input Log and thr Error Log data with a bit of SQL. As the meerkats might say, 'simples'.

When you get beyond simple flows my experience is to simulate the action of an exception with a throw node used where the exception might occur.
Then you can see what really happens.
It does not take long to knock up a POC flow to prove this sort of stuff.
_________________
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.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » floeorder node
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.