My Oracle Support Banner

OMC : APMAgent For JBOSS Failing With Error - "Failed to get container information after waiting for 600 seconds" (Doc ID 2783487.1)

Last updated on JUNE 10, 2021

Applies to:

Oracle Management Cloud - Version N/A to N/A [Release 1.0]
Information in this document applies to any platform.

Symptoms

Oracle Management Cloud (OMC), APMAgent for JBOSS was configured, but the startup does not work.

Error stack observed from <APM agent install dir>/apmagent/logs/AgentErrors.log:

<2021-06-07T16:40:23.256-0400> INFO <exceptions> Exception log is initialized
<2021-06-07T16:50:23.864-0400> SEVERE <exceptions> Failed to get container information after waiting for 600 seconds <Ref: KMA3KD2EQBRPS7U2APVI62NTIYMZTG4S>
<2021-06-07T16:50:23.864-0400> SEVERE <exceptions> Failed to get container information after waiting for 600 seconds <Ref: KMA3KD2EQBRPS7U2APVI62NTIYMZTG4S>
<2021-06-07T16:50:23.870-0400> SEVERE <exceptions> Failed to get container information <Ref: N7WK6QQEE23Z7V5OBL6K6FLTIPAOALEZ>
oracle.apmaas.agent.utility.container.ContainerNotReadyException: jboss.as:management-root=server
at oracle.apmaas.agent.utility.container.jboss.Jboss7ContainerInformation.retrieveVersionInfo(Jboss7ContainerInformation.java:95)
at oracle.apmaas.agent.utility.container.jboss.JbossContainerInformationBase.getInfo(JbossContainerInformationBase.java:49)
at oracle.apmaas.agent.utility.container.jboss.Jboss7ContainerInformation.<init>(Jboss7ContainerInformation.java:23)
at sun.reflect.GeneratedConstructorAccessor2.newInstance(Unknown Source)
.
<2021-06-07T16:50:23.872-0400> SEVERE <exceptions> Agent failed to start <Ref: V4MICVTAMINVQDFRXETT34PQ2WZVARU7>

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
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.