Atomikos Forum

Hi,
can somebody tell me if the following scenario is supported by Atomikos TransactionsEssentials or maybe by another product(even if it is a comercial one)

I have 1 transaction and 2 operations(o1, op2):
1) I start the transaction and perform op1.
2) Before performing op2 I shut down the application server.
3) After starting up the server, I want to continue with op2 and commit the entire transaction.

Is this possible? Is there a way to persist the transaction, suspend it and resume it again?
Suspend and resume work fine if I don't shut down the application server.

Thanks in advance,
Paul

Paul,

Though technically possible, we do not currently support resuming a transaction after restart. Some reasons for that:

-it is not supported by JTA/XA
-it would require your application to maintain workflow state of what things were completed
-it would require your application to restore the thread-to-transaction maps after restart

In other words: your application would have to be a workflow engine.

Our transaction model is as follows: on restart, we will always terminate (rollback/cancel) any pending active transactions. This allows your application to start with a clean state, and this is the easiest abstraction possible.

Why do you want this kind of feature?

Guy,
I've already integrated the transactions with a workflow engine and I use 2 phase-commit protocol.
Taken this into considerantion, do I have any options?

Can you please detail why resuming a transaction after restart is not supported by JTA/XA?

Best regards,
Paul