'transaction' nodes cannot be enclosed within 'clientRequest' nodes - Weblogic
This is a discussion on 'transaction' nodes cannot be enclosed within 'clientRequest' nodes - Weblogic ; Hi!
I have a ClientRequest with Response JPD that inserts some registers in a D=
B. The number of registers varies but sometimes, when this number is big I =
get an exception caused by the transaction (a timeout).
Is ...
-
'transaction' nodes cannot be enclosed within 'clientRequest' nodes
Hi!
I have a ClientRequest with Response JPD that inserts some registers in a D=
B. The number of registers varies but sometimes, when this number is big I =
get an exception caused by the transaction (a timeout).
Is there a way to perform a commit after inserting each register? If I put =
a transaction block in the process I get a "'transaction' nodes cannot be e=
nclosed within 'clientRequest' nodes" message.
Thanks in advance!
-
Re: 'transaction' nodes cannot be enclosed within 'clientRequest' nodes
Synchronous processes run within the same transaction as there parent, so t=
hey shouldn't take control of it. If you want to force a commit in your pro=
cess, make it an asynchronous process, WLI will let you insert explicit tra=
nsaction boundaries.
-
Re: 'transaction' nodes cannot be enclosed within 'clientRequest' nodes
And if making it an asynchronous process is a problem for you, you can also=
keep it synchronous but move the database insertions to another asynchrono=
us process. The original process will simply loop over the entries you want=
to insert and call each time the sub-process. You don't need any explicit =
transaction in the asynchronous sub-process, it will commit each time it fi=
nishes.
-
Re: 'transaction' nodes cannot be enclosed within 'clientRequest' nodes
Thanks a lot!!
> And if making it an asynchronous process is a problem
> for you, you can also keep it synchronous but move
> the database insertions to another asynchronous
> process. The original process will simply loop over
> the entries you want to insert and call each time the
> sub-process. You don't need any explicit transaction
> in the asynchronous sub-process, it will commit each
> time it finishes.