rollback-transaction

DRAFT
Previous Next Contents

rollback-transaction

rolls back the named transaction

Synopsis

asadmin [asadmin-options] rollback-transaction [--help]
[--target target]
transaction_id

Description

The rollback-transaction subcommand rolls back the named transaction.

Before you can roll back a transaction, you must do the following:

  1. Enable monitoring using the set subcommand. For example:

asadmin> set clstr1-config.monitoring-service.module-monitoring-levels.transaction-service=HIGH

  1. Use the freeze-transaction-service subcommand to halt in-process transactions.

  2. Look up the active transactions using the get subcommand with the --monitor option. For example:

asadmin> get --monitor inst1.server.transaction-service.activeids-current

This subcommand is supported in remote mode only.

Options

asadmin-options

Options for the asadmin utility. For information about these options, see the asadmin(1M) help page.

--help
-?

Displays the help text for the subcommand.

--target

This option specifies the target on which you are rolling back the transactions. Valid values are server or any other clustered or stand-alone instance.

Operands

transaction_id

Identifier for the transaction to be rolled back.

Examples

Example 1   Using rollback-transaction command

% asadmin rollback-transaction 0000000000000001_00
Command rollback-transaction executed succeessfully

Exit Status

0

command executed successfully

1

error in executing the command

See Also

asadmin(1M)

freeze-transaction-service(1), recover-transactions(1), unfreeze-transaction-service(1),

"Administering Transactions" in GlassFish Server Open Source Edition Administration Guide

"http://docs.oracle.com/javaee/7/tutorial/doc/transactions.html[Transactions]" in The Java EE 8 Tutorial

Previous Next Contents
Eclipse Foundation Logo  Copyright © 2019, Oracle and/or its affiliates. All rights reserved.

DRAFT