236/461

## rollback-transaction

rolls back the named transaction

Synopsis

    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

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

3. 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

`--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

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

asadmin(1M)

"Administering Transactions" in Oracle GlassFish Server Administration Guide

"Transactions" in The Java EE 6 Tutorial