Admin Console and EJB t3 Calls to Cluster Hanging when One of the Physical Servers in the Cluster is Down
Last updated on OCTOBER 23, 2017
Applies to:Oracle WebLogic Server - Version 10.3 and later
Information in this document applies to any platform.
***Checked for relevance on 19-Aug-2015***
The admin console and EJB t3 calls to the cluster are hanging when one of the physical servers in cluster is down or unavailable (disconnected from network).
For example if you have a domain with Admin Server and 2 Managed Server as part of a Cluster (horizontal cluster), Admin and one Managed server running on one physical machine, e.g., Machine A and second Managed server running on other physical machine, e.g., Machine B.
If Machine B on which second managed server is running is powered down or disconnected from the network, refreshing the admin console for getting server status is taking around 3 minutes. At the same time, t3 calls to the cluster address intermittently hang for 3 minutes. If Machine B is powered on or connected back to network admin console and t3 calls start working fine, no issues.
This issue happens with or without node manager setup.
Below is exception trace observed in thread dumps of Admin Server at the time of issue (stack trace from thread dump may vary based on domain configuration and node manager setup). See <Note 1098691.1> for instructions on how to create a thread dump.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms