
en.help.task-migrate-ejb-timers.html Maven / Gradle / Ivy
Show all versions of console-cluster-plugin Show documentation
To Migrate EJB Timers
If a GlassFish Server instance is stopped, Enterprise JavaBeans (EJB) technology timers that are installed on that instance also stop running. If the instance was stopped abnormally or unexpectedly, To enable these timers run while the instance is stopped, you must migrate the timers to a running server instance in the cluster.
-
In the navigation tree, expand the Clusters node.
-
Under the Clusters node in the navigation tree, select the cluster.
The General Information page for the cluster opens.
-
On the General Information page, click Migrate EJB Timers.
The Migrate EJB Timers page opens.
Note:
If all instances in the cluster are running, the Migrate EJB Timers button is deactivated.
To assist you in migrating timers, the Migrate EJB Timers page contains a table of EJB timers with the following information.
- Server Name
-
List of GlassFish Server instances in the cluster.
- Timer Count
-
Number of persistent timers on each instance.
-
On the Migrate EJB Timers page, select the instance from which and to which to migrate the timers.
-
From the Source drop-down list, select the stopped instance from which to migrate the timers.
-
From the Destination drop-down list, select the running instance to which to migrate the timers.
-
Click OK.
If the source instance is running or if the destination instance is not running, the Administration Console displays an error message.
Copyright © 2005, 2017, Oracle and/or its affiliates. All rights reserved. Legal Notices