JMS Server Migration Policy
(Doc ID 2447923.1)
Last updated on JUNE 12, 2023
Applies to:Oracle WebLogic Server - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
How does JMS Migration actually work?
We have two nodes in a cluster environment and they are configured to "Auto-Migrate" in the event of one node going down.
On Aug 5th 2018, we had a change where we had to perform the restart of the Application.
The Admin Server was started up first and then from the console we checked (selected) both the nodes (MS1 and MS2) and clicked on the "START" option.
Both the nodes (MS1 and MS2) were getting started up simultaneously but the MS1 came earlier at 10:13 AM IST and then after a delay of 3 minutes, at 10:16 AM IST MS2 node came up.
The below table illustrates how the Migration happened and the timelines it took for the migration to happen.
Name MigratedFrom MigratedTo MigrationStartTime MigrationEndTime
MigrationData-PATHSERVICE2 MS1 MS1 Aug 5th 2018 - 10:13:03 IST Aug 5th 2018 - 10:47:03 IST
MigrationData-Store_MS1 MS1 MS1 Aug 5th 2018 - 10:13:42 IST Aug 5th 2018 - 10:28:57 IST
MigrationData-Store_MS2 MS2 MS1 Aug 5th 2018 - 10:13:42 IST Aug 5th 2018 - 10:46:41 IST
MigrationData-Store_MS2 MS1 MS2 Aug 5th 2018 - 10:50:26 IST Aug 5th 2018 - 10:50:47 IST
From the above table the "MigrationData-Store_MS2" module should be pointing to MS2 (MS2) but as the MS1 was started up first and MS2 came after a delay of 3 minutes this module also started to Migrate and point to MS1 (MS1).
If both of the Managed Nodes were getting started up and there is delay of 3 to 5 min at the time of the start up will these modules point to the available Node only? Does the Nodemanger not know that the other node (MS2) is getting started up and Migratable Server has to wait for its start up and point to MS2 instead MS1?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document