WLS Cluster debugging – some tips by Jon Petter Hjulstad

Posted: September 10, 2016 in WebLogic
Tags: , , , , , , ,

 

Some tips when debugging WLS cluster stability

In one environment we had problems with cluster stability – and there were unnecessary migrations of JMS Servers.

Here are some settings that gave more info in logs. Set the following for the JVM:

-Dweblogic.debug.DebugServerMigration=true -Dweblogic.debug.DebugSingletonServices=true 

Change the below setting to DEBUG

 Home >Summary of Servers >AdminServer >Logging >General >Advanced >Minimum severity to log: 

enable below debugs from the weblogic admin console.

 Debug >weblogic >core 

cluster Collapse Node

 
 DebugAsyncQueue 
 DebugCluster 
 DebugClusterAnnouncements 
 DebugClusterFragments 
 DebugClusterHeartbeats 
 DebugLeaderElection 
 DebugReplication 
 DebugReplicationDetails 

Change the logging severity to Debug

 Servers-->Server_name-->Logging-->Advanced--> Standard out :Severity level:Debug 
 Log file :Severity level:Debug 

Restart.

Also look at Cluster » Monitoring » Summary to see the number of sent / received / retransmitted. For a healthy system sent and received should be almost same – and retransmissions low. Read the complete article here.

WebLogic Partner Community

For regular information become a member in the WebLogic Partner Community please visit: http://www.oracle.com/partners/goto/wls-emea ( OPN account required). If you need support with your account please contact the Oracle Partner Business Center.

Blog Twitter LinkedIn Forum Wiki

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s