SOLVED System Resources Problem - Some JVM Managed Servers not showing value
-
Hi again,
In our production domain, System Resources dashboard does not shows somes WebLogic managed server’s value. Attached screen capture below. It’s JVM Memory is displayed “0” all the time. Is it bug or something else?
-
Hi Van,
the MemoryImpl JMX MBean group have not been listed on Metric Browser. Because, JMX monitoring port is added on ManagedServer_1 JVM as below:
-Xmanagement:port=7094,ssl=false,authenticate=false,autodiscovery=trueIf you remove this JVM argument from ManagedServer_1 you are going to able to Monitor ManagedServer_1’s JVM metrics on JVM System Resources dashboard.
Could you please try this solution offer and let us know the result.
Regards…
WLSDM Community Support Team
-
Hi,
We have tested your issue and did not faced as you reported.
Can you go to “WLSDM Console > Configuration > Metric Browser” page and open “Add New Metrics” window. Then check MemoryImpl JMX by searching in “Metric Group” for the relevant WebLogic Managed Servers. And let us know the result?
Regards…
WLSDM Community Support Team
-
@wlsdmadmin said:
Hi,
We have tested your issue and did not faced as you reported.
Can you go to “WLSDM Console > Configuration > Metric Browser” page and open “Add New Metrics” window. Then check MemoryImpl JMX by searching in “Metric Group” for the relevant WebLogic Managed Servers. And let us know the result?
Regards…
Hi,
I have checked the “MemoryImpl” JMX for ManagedServer_1 and it is not listed, but I can see MemoryImpl on AdminServer. So, what is the difference?
-
@vanrussell_nl
Hi, could you please share output of below commands?- ps -ef | grep java | grep Admin
- ps -ef | grep java | grep ManagedServer_1
WLSDM Community Support Team
-
@wlsdmadmin
AdminServer:
weblogic 9717 9663 3 Dec26 ? 01:44:31 /data1/weblogic/java/jrockit/jrockit-jdk1.6.0_29-R28.1.5-4.0.1/bin/java -jrockit -Xms512m -Xmx768m -Dweblogic.Name=AdminServer -Djava.security.policy=/data1/weblogic/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.policy -Dweblogic.ProductionModeEnabled=true -Dweblogic.ProductionModeEnabled=true -da -Dplatform.home=/data1/weblogic/Oracle/Middleware/wlserver_10.3 -Dwls.home=/data1/weblogic/Oracle/Middleware/wlserver_10.3/server -Dweblogic.home=/data1/weblogic/Oracle/Middleware/wlserver_10.3/server -Dweblogic.management.discover=true -Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dwlw.logErrorsToConsole=false -Dweblogic.ext.dirs=/data1/weblogic/Oracle/Middleware/patch_wls1036/profiles/default/sysext_manifest_classpath:/data1/weblogic/Oracle/Middleware/patch_ocp371/profiles/default/sysext_manifest_classpath -Dweblogic.system.BootIdentityFile=/data1/weblogic/domains/PROD-DOMAIN/boot.properties -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=11222,server=y,suspend=n -da -Dplatform.home=/data1/weblogic/Oracle/Middleware/wlserver_10.3 -Dwls.home=/data1/weblogic/Oracle/Middleware/wlserver_10.3/server -Dweblogic.home=/data1/weblogic/Oracle/Middleware/wlserver_10.3/server -Dweblogic.management.discover=true -Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dwlw.logErrorsToConsole=false -Dweblogic.ext.dirs=/data1/weblogic/Oracle/Middleware/patch_wls1036/profiles/default/sysext_manifest_classpath:/data1/weblogic/Oracle/Middleware/patch_ocp371/profiles/default/sysext_manifest_classpath weblogic.Server
**ManagedServer_1:**weblogic 9874 9819 3 Dec26 ? 01:32:06 /data1/weblogic/java/jrockit/jrockit-jdk1.6.0_29-R28.1.5-4.0.1/bin/java -jrockit -Xms512m -Xmx512m -Dweblogic.Name=ManagedServer_1 -Djava.security.policy=/data1/weblogic/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.policy -Dweblogic.ProductionModeEnabled=true -Dweblogic.system.BootIdentityFile=/data1/weblogic/domains/PROD-DOMAIN/servers/ManagedServer_1/data/nodemanager/boot.properties -Dweblogic.nodemanager.ServiceEnabled=true -Dweblogic.security.SSL.ignoreHostnameVerification=true -Dweblogic.ReverseDNSAllowed=false -Xmanagement:port=7094,ssl=false,authenticate=false,autodiscovery=true -javaagent:/data1/weblogic/domains/PROD-DOMAIN/wlsdm_agent/wlsdm_agent.jar -Dwlsdm.agent.logger.level=ALL -Xms1024m -Xmx1024m -XX:PermSize=256m -XX:MaxPermSize=512m -Dweblogic.Stdout=/data1/weblogic/wlslogs/PROD-DOMAIN/ManagedServer_1.out -Dweblogic.Stderr=/data1/weblogic/wlslogs/PROD-DOMAIN/ManagedServer_1_err.out -da -Dplatform.home=/data1/weblogic/Oracle/Middleware/wlserver_10.3 -Dwls.home=/data1/weblogic/Oracle/Middleware/wlserver_10.3/server -Dweblogic.home=/data1/weblogic/Oracle/Middleware/wlserver_10.3/server -Dweblogic.management.discover=false -Dweblogic.management.server=http://10.100.3.227:1100 -Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dwlw.logErrorsToConsole=false -Dweblogic.ext.dirs=/data1/weblogic/Oracle/Middleware/patch_wls1036/profiles/default/sysext_manifest_classpath:/data1/weblogic/Oracle/Middleware/patch_ocp371/profiles/default/sysext_manifest_classpath weblogic.Server -
Hi Van,
the MemoryImpl JMX MBean group have not been listed on Metric Browser. Because, JMX monitoring port is added on ManagedServer_1 JVM as below:
-Xmanagement:port=7094,ssl=false,authenticate=false,autodiscovery=trueIf you remove this JVM argument from ManagedServer_1 you are going to able to Monitor ManagedServer_1’s JVM metrics on JVM System Resources dashboard.
Could you please try this solution offer and let us know the result.
Regards…
WLSDM Community Support Team
-
@wlsdmadmin said:
-Xmanagement:port
I have removed Xmanagement:port JVM argument and the problem is solved. But, sometime we user JRockit mission control for monitoring. Is it possible to make two option work properly?
Attached working screen capture below:
-
Hi,
It’s an WebLogic issue and unfortunately WebLogic does not serve JMX value at the same time. Anymore, you don’t need to live Java Mission Control connection. Just keep using WLSDM
Best Regard…
