WLS Cluster debugging - some tips

May 19, 2016

Reading time ~1 minute

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.

Jon Petter is Department Manager for Middleware at SYSCO. Building an organization of skilled Oracle Middleware experts, with a focus on Oracle SOA Suite, Weblogic, Oracle Service Bus, BPM Suite, BAM, Oracle Event Processing. He has worked with Oracle products since 1997, and has worked with some of the larger SOA customers in Norway. Board member of the Oracle User Group Norway (OUGN), and Oracle ACE Associate.

Get “non XML” file on request based on a file name and send it via HTTP POST with OSB 12c

Requirement is fairly simple, there is a need to transfer a “non XML” file (in this specific case .pdf document) based on the file name w...… Continue reading