Author |
Message
|
angka |
Posted: Wed May 16, 2007 7:24 am Post subject: Output node transaction |
|
|
Chevalier
Joined: 20 Sep 2005 Posts: 406
|
Hi all,
I am using Output node with destination list. my destination list consists of 2 remote queues, A and B pointing to transmission queue Ax and Bx. however when one of the transmission queue eg Bx is full, the flow roll back the whole transaction and put to DLQ even when Ax is not full. Is there a way to complete the transaction when putting to Ax and send the message for Bx to the DLQ instead?
by rolling back the whole transaction due to one full transmission queue is undesirable.
Thanks |
|
Back to top |
|
 |
Vitor |
Posted: Wed May 16, 2007 8:00 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
Change the output syncpoint mode to make the put outside syncpoint. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
jbanoop |
Posted: Wed May 16, 2007 9:51 am Post subject: |
|
|
Chevalier
Joined: 17 Sep 2005 Posts: 401 Location: SC
|
but then you want it to rollback if both the puts fail ..dont you ...
my opinion is to use a flow order and if the put to the first output Q fails catch and handle it (like setting some variable) using try-catch node and then try to put to the second output Q.
use a try-catch to catch any exception and then check the env to see if the first put failed .. if not complete successfully else throw to rollback the transaction. |
|
Back to top |
|
 |
Vitor |
Posted: Wed May 16, 2007 11:40 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
jbanoop wrote: |
but then you want it to rollback if both the puts fail ..dont you ...
|
He said he didn't...
...but I thought it was odd as well.  _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
elvis_gn |
Posted: Thu May 17, 2007 12:03 am Post subject: |
|
|
 Padawan
Joined: 08 Oct 2004 Posts: 1905 Location: Dubai
|
Hi angka,
Vitor's suggestion should be far more simpler....Just set the Transaction mode on the Output node as 'no'...In this way it will put to A and commit...irrespective of what happens to B after that,...
Regards. |
|
Back to top |
|
 |
angka |
Posted: Thu May 17, 2007 12:12 am Post subject: |
|
|
Chevalier
Joined: 20 Sep 2005 Posts: 406
|
Hi,
If both the put fail i will send both the messages to the DLQ. I dun need it to roll back.
So I believe this shld be wat I want. Thanks.
Rgds. |
|
Back to top |
|
 |
angka |
Posted: Thu May 17, 2007 12:14 am Post subject: |
|
|
Chevalier
Joined: 20 Sep 2005 Posts: 406
|
Hi,
If both the put fail i will send both the messages to the DLQ. I dun need it to roll back.
So I believe this shld be wat I want. Thanks.
Rgds. |
|
Back to top |
|
 |
|