This content has been marked as final. Show 4 replies
Depends on your process. Sounds like you have designed a synchronous (request / reply) transient (no breakpoints) process.
If synchronous ( with no breakpoint activities) process executes a rollback, you will not ever see anything in the console. The reason for this, is that the BPEL Process is executed in the clients thread. Any rollback will cause dehydration not to occur, and the client will receive an error message. It is up to the client to handle the error. Synchronous transient processes will not show up in the console, as no data was ever committed to the database. The console only displays data that is in the database (and committed).
The behavior for processes that have been designed as asyncronous and/or durable is different... if you need to see something in the console, you may need to think about redesigning your process.
Do you NEED to see something in the console? Or are you just expecting to?
Edited by: Charles Poulsen on Aug 28, 2008 7:02 AM
I am unable to rollback the dbtransactions.
some times it is working and some times not!!!!
I am using one file read and six DB adapters to insert data into tables.
I am using the transaction=participate at global level.
I am using two scopes (total three the one including the main) in the first one receive activity is there and in the same scope i dragged the second scope and kept all DB adapters in that.
Now i am catching exceptions using catchAll and throwing bpelx:rollback in the second scope and catching the rolback in first scope and compensating the activities done in the second scope.
It is not working..
Plz provide me with the consistent solution !!!!