High Availability with WebLogic Clusters - Oracle WebLogic Server 12c Advanced Administration - page 48

cmo.setStuckThreadCount(0)
activate()
exit()
Using Unicast for cluster communications
The Oracle WebLogic Server 12 c can use either Multicast or Unicast for cluster
communications. Since WebLogic version 10, the default cluster communication is the Unicast.
To improve Unicast reliability it's recommended to enable two extra configurations.
Getting ready
The first thing is to add a JVM argument to every WebLogic Managed Server instance of the
cluster. The Administration Server must be running to make the changes.
After adding the JVM argument, the config.xml configuration file must be manually edited
to make the second change. Therefore you will need to make sure every WebLogic Server
instance is down, including the Administration Server.
How to do it...
Add the JVM argument:
1. Access the Administration Console with your web browser at http://prod01.
domain.local:7001/console .
2. Click on the Lock & Edit button to start a new edit session.
3. Navigate to Configuration | Server Start by clicking on the WebLogic Server name,
then on the Server Start tab.
4. Add the argument -Dweblogic.unicast.HttpPing=true to the Arguments field.
The argument must be added to all Managed Server instances of PROD_Cluster :
PROD_Server01 , PROD_Server02 , PROD_Server03 , and PROD_Server04 . Click
on the Save button for every change.
5. Click on the Activate Changes button.
6. Navigate to Domain | Control by clicking on the PROD_DOMAIN link to the left and
then on the Control tab.
7. Select and shut down all servers from the list.