Network Deployment (Distributed operating systems), v8.0 > Administer applications and their environment > Administer Transactions > Administer the transaction service


Manage active and prepared transactions


Under exceptional circumstances, for example, during performance and load testing, transactions may not commit or roll back automatically. In these cases we can intervene to commit or rollback.

To manage active and prepared transactions for an application server, use the administrative console...

...where...

State Information Action
Manual transactions Local or global id
Associated resource 		Commit or roll back
Retry transactions Local or global id
Committing or rolling back
Associated resource 		Finish (stop retrying)
Heuristic transactions Local or global id
Heuristic outcome
Associated resource 		Clear the transaction from the list.
Imported prepared transactions Local or global id
Associated resource 		Commit or roll back

To display a snapshot of the transactions in a specific state

Transactions completed in this manner are recorded as having completed in the transaction service logs for that server, so they will not be eligible for recovery during server start up. You are responsible for cleaning up any in-doubt transactions on the affected resource managers.

Finally, it should be mentioned, that in a pinch, to remove all pending transactions, stop the appserver and run...

Needless to say, do this only for non-production appservers.


Related

Manage active and prepared transactions using wsadmin.sh
Configure transaction properties for an application server
Use the transaction service

+

Search Tips   |   Advanced Search