Splunk AppDynamics

Problems adding agent to Oracle Service Bus 11

Hi All

I'm adding a java agent (4.5.1.23676) to an oracle service bus instance (running weblogic 10.3 and jdk1.6.0_161) using the normal arguments:

-javaagent:/var/(...)/appdynamics/osb_mserver_11/javaagent.jar

However I'm getting the following error:

Full Agent Registration Info Resolver using selfService [true]
Full Agent Registration Info Resolver using selfService [true]
Full Agent Registration Info Resolver using application name [IOTPlatform]
Full Agent Registration Info Resolver using tier name [OSB]
Full Agent Registration Info Resolver using node name [osb_mserver_12]
Install Directory resolved to[/var/(...)/appdynamics/osb_mserver_12]
ERROR StatusLogger No log4j2 configuration file found. Using default configuration: logging only errors to the console.
2.678: [GC 2.678: [ParNew: 68160K->8512K(76672K), 0.0146020 secs] 68160K->11105K(6282944K), 0.0152460 secs] [Times: user=0.03 sys=0.00, real=0.01 secs]
[Thread-0] Wed Aug 29 17:13:22 CEST 2018[DEBUG]: AgentInstallManager - Full Agent Registration Info Resolver is running
[Thread-0] Wed Aug 29 17:13:22 CEST 2018[INFO]: AgentInstallManager - Full Agent Registration Info Resolver using selfService [true]
[Thread-0] Wed Aug 29 17:13:22 CEST 2018[INFO]: AgentInstallManager - Full Agent Registration Info Resolver using selfService [true]
[Thread-0] Wed Aug 29 17:13:22 CEST 2018[INFO]: AgentInstallManager - Full Agent Registration Info Resolver using application name [IOTPlatform]
[Thread-0] Wed Aug 29 17:13:22 CEST 2018[INFO]: AgentInstallManager - Full Agent Registration Info Resolver using tier name [OSB]
[Thread-0] Wed Aug 29 17:13:22 CEST 2018[INFO]: AgentInstallManager - Full Agent Registration Info Resolver using node name [osb_mserver_12]
[Thread-0] Wed Aug 29 17:13:22 CEST 2018[DEBUG]: AgentInstallManager - Full Agent Registration Info Resolver finished running
[Thread-0] Wed Aug 29 17:13:22 CEST 2018[INFO]: AgentInstallManager - Agent runtime directory set to [/var/(..)/appdynamics/osb_mserver_12/ver4.5.1.23676]
[Thread-0] Wed Aug 29 17:13:22 CEST 2018[INFO]: AgentInstallManager - Agent node directory set to [osb_mserver_12]
[Thread-0] Wed Aug 29 17:13:22 CEST 2018[INFO]: JavaAgent - Using Java Agent Version [Server Agent #4.5.1.23676 v4.5.1 GA compatible with 4.4.1.0 r8b0e9c14b81cb3f59942756e94963ab66fc53a16 master]
[Thread-0] Wed Aug 29 17:13:22 CEST 2018[INFO]: JavaAgent - Running IBM Java Agent [No]
[Thread-0] Wed Aug 29 17:13:22 CEST 2018[INFO]: JavaAgent - Java Agent Directory [/var/(..)/appdynamics/osb_mserver_12/ver4.5.1.23676]
[Thread-0] Wed Aug 29 17:13:22 CEST 2018[INFO]: JavaAgent - Java Agent AppAgent directory [/var/(..)/appdynamics/osb_mserver_12/ver4.5.1.23676]
Agent Logging Directory [/var/(..)/appdynamics/osb_mserver_12/ver4.5.1.23676/logs/osb_mserver_12]

Could not start Java Agent, Disabling !!!!!javax.xml.parsers.FactoryConfigurationError: Provider weblogic.xml.jaxp.RegistryDocumentBuilderFactory not found ,Please check log files

javax.xml.parsers.FactoryConfigurationError: Provider weblogic.xml.jaxp.RegistryDocumentBuilderFactory not found
        at javax.xml.parsers.DocumentBuilderFactory.newInstance(DocumentBuilderFactory.java:129)
        at org.apache.logging.log4j.core.config.xml.XmlConfiguration.newDocumentBuilder(XmlConfiguration.java:82)
        at org.apache.logging.log4j.core.config.xml.XmlConfiguration.<init>(XmlConfiguration.java:140)
        at com.singularity.ee.agent.util.log4j.K.getConfiguration(K.java:93)
        at com.singularity.ee.agent.util.log4j.K.getConfiguration(K.java:98)
        at org.apache.logging.log4j.core.config.ConfigurationFactory.getConfiguration(ConfigurationFactory.java:254)
        at org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:394)
        at org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:411)
        at com.singularity.ee.agent.appagent.kernel.JavaAgent.d(JavaAgent.java:925)
        at com.singularity.ee.agent.appagent.kernel.JavaAgent.b(JavaAgent.java:805)
        at com.singularity.ee.agent.appagent.kernel.JavaAgent.initialize(JavaAgent.java:528)
        at com.singularity.ee.agent.appagent.kernel.JavaAgent.initialize(JavaAgent.java:329)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at com.singularity.ee.agent.appagent.AgentEntryPoint$1.run(AgentEntryPoint.java:655)

Does anyone knows how to solve the above exception? I have already look around a little bit here and in google but could not find any usefull information.

Thanks in advance

Best regards

Labels (1)
Tags (1)
0 Karma
1 Solution

Narendra_Chaluc
Engager

Hi Joao,

   Can you restart the JVM by including the below startup parameter to resolve the issue.

-Dappdynamics.agent.log4j2.disabled=true

Thanks

Naren

View solution in original post

Narendra_Chaluc
Engager

Hi Joao,

   Can you restart the JVM by including the below startup parameter to resolve the issue.

-Dappdynamics.agent.log4j2.disabled=true

Thanks

Naren

Thank you! It worked!
0 Karma
Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.
Get Updates on the Splunk Community!

Introduction to Splunk AI

How are you using AI in Splunk? Whether you see AI as a threat or opportunity, AI is here to stay. Lucky for ...

Splunk + ThousandEyes: Correlate frontend, app, and network data to troubleshoot ...

Are you tired of troubleshooting delays caused by siloed frontend, application, and network data? We've got a ...

Maximizing the Value of Splunk ES 8.x

Splunk Enterprise Security (ES) continues to be a leader in the Gartner Magic Quadrant, reflecting its pivotal ...