| Author |
Message
|
| rsmart |
 Posted: Wed Feb 10, 2010 7:53 am Post subject: Error: Transaction will commit but an automatic trans exists |
 |
|
Novice
Joined: 27 May 2009
Posts: 10
|
Transaction will be committed, but a pending automatic transaction exists
I get this error when I try to update a table using a subflow that is placed at the end of a message flow. The message wich enters the subflow is coming from a node wich propagates to other nodes and OutputNodes. Any help would be appreciated. |
|
| Back to top |
|
 |
| bhanumb |
| Posted: Sun Jun 24, 2012 6:32 am Post subject: Any solution for this... |
|
|
Newbie
Joined: 24 Jun 2012
Posts: 2
|
Hi
I am also facing the same issue....can any one having solution for this error "Transaction will be committed, but a pending automatic transaction exists"... |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sun Jun 24, 2012 7:53 am Post subject: Re: Any solution for this... |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| bhanumb wrote: |
Hi
I am also facing the same issue....can any one having solution for this error "Transaction will be committed, but a pending automatic transaction exists"... |
A lot more information would be quite more helpful... like:
I have a flow where some nodes write to the DB. Some of those nodes participate in the flow transaction, some do not. When I go over flow node xyz that does/ does not participate in the transaction this is the message I get... All nodes talking to the DB have the same DB name on it.... 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Mon Jun 25, 2012 5:03 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
Opening two year old posts are not helpful. The product has changed alot in the last two years and your root cause may not be the same as the original poster's root cause.
Take a user trace. Post the results in your own topic using [c od e ] tags. Don't hijack other peoples threads.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| bhanumb |
| Posted: Mon Jun 25, 2012 11:44 am Post subject: |
|
|
Newbie
Joined: 24 Jun 2012
Posts: 2
|
Hi fjb_saper
Thanks for your reply,The Actual Problem is
In my flow I am using 2 compute nodes like X and Y.In node X am doing something and propagating to node Y which does Oracle DB INSERT to table1 and Transaction Property of node Y is "commit".
For first 2 propagates I am able to insert the data in DB, but for 3rd time before propagating to node Y am doing a SELECT query to other table like table2 and able to fetch data, After fetching I am propagating to node Y then I am getting this error message, while control going to node Y...
Transaction property of node X is "Automatic", but I tried keeping "commit" also but error persists.... 
And my flow initiates with File Input node for which Transaction mode is "no" and tried keeping "yes" also but error is same...
My MB Toolkit version is 6.1.0.4 |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Jun 25, 2012 12:54 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Now we are going somewhere:
You have node x and node y.
Node y is doing a DB insert
Node x is doing a conditional DB select.
If node x does not have a commit attribute (same transaction attribute as node y) you cannot use the same DSN name for the DB (it's somewhere in the info center... look it up) Even though i is the same DB you need to either set the same transactional attributes, or use 2 different DSNs for the same DB.
Now I'd be extremely careful about deadlocks using that second alternative...
Working as designed.
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
