EMagent is deployed on target host. Target WLS is discovered.
But only the general information about WLS is visible on EMUI. Monitoring details like JDBC, applications, JMS resources etc. are all empty.
emagentfetchlet.trc contains
2011-06-16 11:54:10,211 [nmefmgr_getJNIFetchlet] WARN JMX.generic logp.251 - IOException: cannot communicate to Target with serviceURL=service:jmx:t3://hostname:6003/jndi/weblogic.management.mbeanservers.runtime for metric weblogic_j2eeserver:server_internal:: Couldn't connect to any host Cause: javax.naming.NamingException: Couldn't connect to any host [Root exception is org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 203 completed: Maybe]
Action: Verify that Target Weblogic Server Domain->Advance settings should contain Platform MBean Server Enabled. Set 'PlatformMBeanServerEnabled' to True and restart the weblogic server.
But only the general information about WLS is visible on EMUI. Monitoring details like JDBC, applications, JMS resources etc. are all empty.
emagentfetchlet.trc contains
2011-06-16 11:54:10,211 [nmefmgr_getJNIFetchlet] WARN JMX.generic logp.251 - IOException: cannot communicate to Target with serviceURL=service:jmx:t3://hostname:6003/jndi/weblogic.management.mbeanservers.runtime for metric weblogic_j2eeserver:server_internal:: Couldn't connect to any host Cause: javax.naming.NamingException: Couldn't connect to any host [Root exception is org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 203 completed: Maybe]
Action: Verify that Target Weblogic Server Domain->Advance settings should contain Platform MBean Server Enabled. Set 'PlatformMBeanServerEnabled' to True and restart the weblogic server.
No comments:
Post a Comment