blob: ec3dede5a96cb365ba22a9c82f5cdea4503989f1 [file] [log] [blame]
type=page
status=published
title=migrate-timers
next=monitor.html
prev=login.html
~~~~~~
= migrate-timers
[[migrate-timers-1]][[GSRFM00211]][[migrate-timers]]
== migrate-timers
Moves EJB timers when a clustered instance was stopped or has crashed
[[sthref1882]]
=== Synopsis
[source]
----
asadmin [asadmin-options] migrate-timers [--help]
[--target target_server_name]
server_name
----
[[sthref1883]]
=== Description
The `migrate-timers` subcommand moves EJB timers to a specified server
when a server instance stops or crashes, if automatic timer migration is
not enabled in the cluster configuration. This subcommand is supported
in remote mode only.
[[sthref1884]]
=== Options
asadmin-options::
Options for the `asadmin` utility. For information about these
options, see the link:asadmin.html#asadmin-1m[`asadmin`(1M)] help page.
`--help`::
`-?`::
Displays the help text for the subcommand.
`--target`::
This is the target server instance. If this option is not specified,
then DAS will find a server instance or multiple server instances. A
migration notification will be sent to the selected server instances.
`--destination`::
This option is deprecated. It works exactly as the `--target` option
does.
[[sthref1885]]
=== Operands
server_name::
This is the server instance on which the timers are currently located.
This server instance should not be running during the migration
process.
[[sthref1886]]
=== Examples
[[GSRFM722]][[sthref1887]]
==== Example 1   Migrating Timers
This example shows how to migrate timers from the server named
`instance1` to a server named `instance2`.
[source]
----
asadmin>migrate-timers --target instance2 instance1
This command was successfully executed.
----
[[sthref1888]]
=== Exit Status
0::
command executed successfully
1::
error in executing the command
[[sthref1889]]
=== See Also
link:asadmin.html#asadmin-1m[`asadmin`(1M)]
link:list-timers.html#list-timers-1[`list-timers`(1)]