HealthStateComponent of JMSServer is showing incorrect Value when monitored from WLST (Doc ID 1434624.1)

Last updated on JUNE 09, 2017

Applies to:

Oracle Weblogic Server - Version 9.2 to 12.1.1.0
Information in this document applies to any platform.

Symptoms


Create a simple domain with admin server with Weblogic, created any number JMS server say (JMSServer-0, JMSServer-1 and JMSServer-2) targeted to Admin Server.

Now we executed the following commands through WLST :-

wls:/offline> connect('weblogic','weblogic1','t3://localhost:7001')
Connecting to t3://localhost:7001 with userid weblogic ...
Successfully connected to Admin Server 'AdminServer' that belongs to domain
'JMS'.

Warning: An insecure protocol was used to connect to the server. To ensure on-the-wire security, the SSL port or Admin port should be used instead.

wls:/JMS/serverConfig> domainRuntime()
Location changed to domainRuntime tree. This is a read-only tree with
DomainMBean as the root.
For more help, use help(domainRuntime)

wls:/JMS/domainRuntime> cd('ServerRuntimes')
wls:/JMS/domainRuntime/ServerRuntimes> cd ('AdminServer')
wls:/JMS/domainRuntime/ServerRuntimes/AdminServer> cd ('JMSRuntime')
wls:/JMS/domainRuntime/ServerRuntimes/AdminServer/JMSRuntime> ls()
dr-- AdminServer.jms

wls:/JMS/domainRuntime/ServerRuntimes/AdminServer/JMSRuntime> cd
('AdminServer.jms')
wls:/JMS/domainRuntime/ServerRuntimes/AdminServer/JMSRuntime/AdminServer.jms>
ls()
dr-- Connections
dr-- JMSServers

-r-- ConnectionsCurrentCount 0
-r-- ConnectionsHighCount 0
-r-- ConnectionsTotalCount 0
-r-- HealthState
Component:null,State:HEALTH_OK,MBean:null,ReasonCode:[]
-r-- JMSServersCurrentCount 4
-r-- JMSServersHighCount 4
-r-- JMSServersTotalCount 4
-r-- Name AdminServer.jms
-r-- Type JMSRuntime

-r-x preDeregister Void :

wls:/JMS/domainRuntime/ServerRuntimes/AdminServer/JMSRuntime/AdminServer.jms>
cd ('JMSServers')
wls:/JMS/domainRuntime/ServerRuntimes/AdminServer/JMSRuntime/AdminServer.jms/JMSServers> cd ('JMSServer-2')
wls:/JMS/domainRuntime/ServerRuntimes/AdminServer/JMSRuntime/AdminServer.jms/JMSServers/JMSServer-2> ls()
.
.
.
-r-- HealthState
Component:JMSServer.JMSServer-2,State:HEALTH_OK,MBean:JMSServer-2,ReasonCode:
[]
.
.
.
-r-- Name JMSServer-2
.
.
.

wls:/JMS/domainRuntime/ServerRuntimes/AdminServer/JMSRuntime/AdminServer.jms/
JMSServers/JMSServer-2> cd('..')
wls:/JMS/domainRuntime/ServerRuntimes/AdminServer/JMSRuntime/AdminServer.jms/JMSServers> cd ('JMSServer-1')
wls:/JMS/domainRuntime/ServerRuntimes/AdminServer/JMSRuntime/AdminServer.jms/JMSServers/JMSServer-1> ls()
.
.
.
-r-- HealthState
Component:JMSServer.JMSServer-2,State:HEALTH_OK,MBean:JMSServer-2,ReasonCode:
[]
.
.
.
-r-- Name JMSServer-1
.
.
.

wls:/JMS/domainRuntime/ServerRuntimes/AdminServer/JMSRuntime/AdminServer.jms/
JMSServers/JMSServer-1> cd('..')
wls:/JMS/domainRuntime/ServerRuntimes/AdminServer/JMSRuntime/AdminServer.jms/JMSServers> cd ('JMSServer-0')
wls:/JMS/domainRuntime/ServerRuntimes/AdminServer/JMSRuntime/AdminServer.jms/JMSServers/JMSServer-0> ls()
.
.
.
-r-- HealthState
Component:JMSServer.JMSServer-2,State:HEALTH_OK,MBean:JMSServer-2,ReasonCode:
[]
.
.
.
-r-- Name JMSServer-0
.
.
.


 
From the above it can be seen that in the Health state Component of JMSServer-0, JMSServer-1 and JMSServer-2 it always displays the name of only one Server JMSServer-2.
 
 
So we can conclude that the health State of the JMSServer:- Component and MBean value shows incorrect JMSServer name.
 

Cause

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