EM12c : ADP/JVMD Agent Deploys successfully but doesn't show up on the Application Dependency and Performance >> Status page or shows the wrong ADMIN URI in the Console
(Doc ID 1907777.1)
Last updated on SEPTEMBER 10, 2021
Applies to:
APM - Application Performance Management - Version 12.1.0.3.0 to 12.1.0.6.0 [Release 12.1]Information in this document applies to any platform.
Symptoms
There are 3 issues reported/seen when using the SDP protocol with the Oracle WebLogic Server (WLS) Domains where the ADP/JVMD agent deployment has to run.
1) ADP/JVMD agent get deployed successfully but doesn't show up on the
UI >> Targets >> Middleware >> Application Dependency and Performance >> Status page.
2) If the ADP/JVMD agent get deployed successfully it won't show up on the APM page or it might show the wrong ADMIN URI.
3) Deployment fails for the ADP agents with the following errors in the logs.
ADP Manager logs
2014/04/03 01:22:35.235,L,2710598,W,Oracle Enterprise Manager:<HOSTNAME>.<DOMAIN_NAME>_7001_pcaqoqoc3psa:BEAJMXMIP9:1 Discovery Thread,BEAMBeanProvider9,Exception connecting to server: wls_spaces1 Skipping...
2014/04/03 01:22:35.235,L,2710599,E,Oracle Enterprise Manager:<HOSTNAME>.<DOMAIN_NAME>_7001_pcaqoqoc3psa:BEAJMXMIP9:1 Discovery Thread,BEAMBeanProvider9,java.io.IOException
2014/04/03 01:22:35.235,L,2710600,E,Oracle Enterprise Manager:<HOSTNAME>.<DOMAIN_NAME>_7001_pcaqoqoc3psa:BEAJMXMIP9:1 Discovery Thread,BEAMBeanProvider9, at weblogic.management.remote.common.ClientProviderBase.makeConnection(ClientProviderBase.java:196)
2014/04/03 01:22:35.235,L,2710601,E,Oracle Enterprise Manager:<HOSTNAME>.<DOMAIN_NAME>_7001_pcaqoqoc3psa:BEAJMXMIP9:1 Discovery Thread,BEAMBeanProvider9, at weblogic.management.remote.common.ClientProviderBase.newJMXConnector(ClientProviderBase.java:84)
2014/04/03 01:22:35.235,L,2710602,E,Oracle Enterprise Manager:<HOSTNAME>.<DOMAIN_NAME>_7001_pcaqoqoc3psa:BEAJMXMIP9:1 Discovery Thread,BEAMBeanProvider9, at javax.management.remote.JMXConnectorFactory.newJMXConnector(JMXConnectorFactory.java:338)
2014/04/03 01:22:35.235,L,2710603,E,Oracle Enterprise Manager:<HOSTNAME>.<DOMAIN_NAME>_7001_pcaqoqoc3psa:BEAJMXMIP9:1 Discovery Thread,BEAMBeanProvider9, at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:247)
2014/04/03 01:22:35.235,L,2710604,E,Oracle Enterprise Manager:<HOSTNAME>.<DOMAIN_NAME>_7001_pcaqoqoc3psa:BEAJMXMIP9:1 Discovery Thread,BEAMBeanProvider9, at com.acsera.mips.jmx.bea.BEAMBeanProvider9.initConnection(BEAMBeanProvider9.java:83)
2014/04/03 01:22:35.235,L,2710605,E,Oracle Enterprise Manager:<HOSTNAME>.<DOMAIN_NAME>_7001_pcaqoqoc3psa:BEAJMXMIP9:1 Discovery Thread,BEAMBeanProvider9, at com.acsera.mips.jmx.bea.BEAMBeanProvider9.discoverContainers(BEAMBeanProvider9.java:417)
2014/04/03 01:22:35.235,L,2710606,E,Oracle Enterprise Manager:<HOSTNAME>.<DOMAIN_NAME>_7001_pcaqoqoc3psa:BEAJMXMIP9:1 Discovery Thread,BEAMBeanProvider9, at com.acsera.mips.jmx.JMXMIP.performDiscovery(JMXMIP.java:236)
2014/04/03 01:22:35.235,L,2710607,E,Oracle Enterprise Manager:<HOSTNAME>.<DOMAIN_NAME>_7001_pcaqoqoc3psa:BEAJMXMIP9:1 Discovery Thread,BEAMBeanProvider9, at com.acsera.mips.jmx.JMXMIP.access$800(JMXMIP.java:21)
2014/04/03 01:22:35.235,L,2710608,E,Oracle Enterprise Manager:<HOSTNAME>.<DOMAIN_NAME>_7001_pcaqoqoc3psa:BEAJMXMIP9:1 Discovery Thread,BEAMBeanProvider9, at com.acsera.mips.jmx.JMXMIP$DiscoveryThread.run(JMXMIP.java:849)
2014/04/03 01:22:35.235,L,2710609,E,Oracle Enterprise Manager:<HOSTNAME>.<DOMAIN_NAME>_7001_pcaqoqoc3psa:BEAJMXMIP9:1 Discovery Thread,BEAMBeanProvider9, at java.lang.Thread.run(Thread.java:662)
2014/04/03 01:22:35.235,L,2710610,E,Oracle Enterprise Manager:<HOSTNAME>.<DOMAIN_NAME>_7001_pcaqoqoc3psa:BEAJMXMIP9:1 Discovery Thread,BEAMBeanProvider9,Caused by: javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3://<IP>:8871: Destination unreachable; nested exception is:
2014/04/03 01:22:35.235,L,2710611,E,Oracle Enterprise Manager:<HOSTNAME>.<DOMAIN_NAME>_7001_pcaqoqoc3psa:BEAJMXMIP9:1 Discovery Thread,BEAMBeanProvider9, java.net.ConnectException: Connection refused; No available router to destination]
2014/04/03 01:22:35.235,L,2710598,W,Oracle Enterprise Manager:<HOSTNAME>.<DOMAIN_NAME>_7001_pcaqoqoc3psa:BEAJMXMIP9:1 Discovery Thread,BEAMBeanProvider9,Exception connecting to server: wls_spaces1 Skipping...
2014/04/03 01:22:35.235,L,2710599,E,Oracle Enterprise Manager:<HOSTNAME>.<DOMAIN_NAME>_7001_pcaqoqoc3psa:BEAJMXMIP9:1 Discovery Thread,BEAMBeanProvider9,java.io.IOException
2014/04/03 01:22:35.235,L,2710600,E,Oracle Enterprise Manager:<HOSTNAME>.<DOMAIN_NAME>_7001_pcaqoqoc3psa:BEAJMXMIP9:1 Discovery Thread,BEAMBeanProvider9, at weblogic.management.remote.common.ClientProviderBase.makeConnection(ClientProviderBase.java:196)
2014/04/03 01:22:35.235,L,2710601,E,Oracle Enterprise Manager:<HOSTNAME>.<DOMAIN_NAME>_7001_pcaqoqoc3psa:BEAJMXMIP9:1 Discovery Thread,BEAMBeanProvider9, at weblogic.management.remote.common.ClientProviderBase.newJMXConnector(ClientProviderBase.java:84)
2014/04/03 01:22:35.235,L,2710602,E,Oracle Enterprise Manager:<HOSTNAME>.<DOMAIN_NAME>_7001_pcaqoqoc3psa:BEAJMXMIP9:1 Discovery Thread,BEAMBeanProvider9, at javax.management.remote.JMXConnectorFactory.newJMXConnector(JMXConnectorFactory.java:338)
2014/04/03 01:22:35.235,L,2710603,E,Oracle Enterprise Manager:<HOSTNAME>.<DOMAIN_NAME>_7001_pcaqoqoc3psa:BEAJMXMIP9:1 Discovery Thread,BEAMBeanProvider9, at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:247)
2014/04/03 01:22:35.235,L,2710604,E,Oracle Enterprise Manager:<HOSTNAME>.<DOMAIN_NAME>_7001_pcaqoqoc3psa:BEAJMXMIP9:1 Discovery Thread,BEAMBeanProvider9, at com.acsera.mips.jmx.bea.BEAMBeanProvider9.initConnection(BEAMBeanProvider9.java:83)
2014/04/03 01:22:35.235,L,2710605,E,Oracle Enterprise Manager:<HOSTNAME>.<DOMAIN_NAME>_7001_pcaqoqoc3psa:BEAJMXMIP9:1 Discovery Thread,BEAMBeanProvider9, at com.acsera.mips.jmx.bea.BEAMBeanProvider9.discoverContainers(BEAMBeanProvider9.java:417)
2014/04/03 01:22:35.235,L,2710606,E,Oracle Enterprise Manager:<HOSTNAME>.<DOMAIN_NAME>_7001_pcaqoqoc3psa:BEAJMXMIP9:1 Discovery Thread,BEAMBeanProvider9, at com.acsera.mips.jmx.JMXMIP.performDiscovery(JMXMIP.java:236)
2014/04/03 01:22:35.235,L,2710607,E,Oracle Enterprise Manager:<HOSTNAME>.<DOMAIN_NAME>_7001_pcaqoqoc3psa:BEAJMXMIP9:1 Discovery Thread,BEAMBeanProvider9, at com.acsera.mips.jmx.JMXMIP.access$800(JMXMIP.java:21)
2014/04/03 01:22:35.235,L,2710608,E,Oracle Enterprise Manager:<HOSTNAME>.<DOMAIN_NAME>_7001_pcaqoqoc3psa:BEAJMXMIP9:1 Discovery Thread,BEAMBeanProvider9, at com.acsera.mips.jmx.JMXMIP$DiscoveryThread.run(JMXMIP.java:849)
2014/04/03 01:22:35.235,L,2710609,E,Oracle Enterprise Manager:<HOSTNAME>.<DOMAIN_NAME>_7001_pcaqoqoc3psa:BEAJMXMIP9:1 Discovery Thread,BEAMBeanProvider9, at java.lang.Thread.run(Thread.java:662)
2014/04/03 01:22:35.235,L,2710610,E,Oracle Enterprise Manager:<HOSTNAME>.<DOMAIN_NAME>_7001_pcaqoqoc3psa:BEAJMXMIP9:1 Discovery Thread,BEAMBeanProvider9,Caused by: javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3://<IP>:8871: Destination unreachable; nested exception is:
2014/04/03 01:22:35.235,L,2710611,E,Oracle Enterprise Manager:<HOSTNAME>.<DOMAIN_NAME>_7001_pcaqoqoc3psa:BEAJMXMIP9:1 Discovery Thread,BEAMBeanProvider9, java.net.ConnectException: Connection refused; No available router to destination]
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |