Java Agent Problem with Jboss 6.1.0.GA and Java Agent v3.9.3.0

[CommunityUser]

Hi,

I've got a problem with Jboss 6.1.0.GA and Java Agent v3.9.3.0 that I'm hoping someone has run into before. This problem is specific to newer versions of the Java Agent, as an older version we had used worked find with this version of Jboss. The details are below:

Jboss Version:

JBoss EAP 6.1.0.GA (AS 7.2.0.Final-redhat-8)

AppDynamics Java Client Version:

Java Agent Version [Server Agent v3.9.3.0 GA #2014-09-23_22-14-15 r05918cd8a4a8a63504a34f0f1c85511e207049b3 20-3.9.3.next]

Error Message:

Install Directory resolved to[/opt/AppDynamics/JavaAgent]

[INFO]: AgentInstallManager - AppDynamics Agent edition [standard]

[DEBUG]: AgentInstallManager - Full Agent Registration Info Resolver is running

[INFO]: AgentInstallManager - Full Agent Registration Info Resolver using application name [Perf]

[INFO]: AgentInstallManager - Full Agent Registration Info Resolver using tier name [ttcom-ws-java]

[INFO]: AgentInstallManager - Full Agent Registration Info Resolver using node name [pdevtttws300]

[DEBUG]: AgentInstallManager - Full Agent Registration Info Resolver finished running

[INFO]: AgentInstallManager - Agent runtime directory set to [/opt/AppDynamics/JavaAgent]

[INFO]: AgentInstallManager - Agent node directory set to [pdevtttws300]

[WARN]: AgentInstallManager - Invalid Edition [Java Agent]. Keeping current edition [STANDARD]

[INFO]: JavaAgent - Using Java Agent Version [Server Agent v3.9.3.0 GA #2014-09-23_22-14-15 r05918cd8a4a8a63504a34f0f1c85511e207049b3 20-3.9.3.next]

[INFO]: JavaAgent - Running IBM Java Agent [No]

[INFO]: JavaAgent - Java Agent Directory [/opt/AppDynamics/JavaAgent]

Agent Logging Directory [/opt/AppDynamics/JavaAgent/logs/pdevtttws300]

Running obfuscated agent

Registered app server agent with Node ID[41539] Component ID[2807] Application ID [769]

Started AppDynamics Java Agent Successfully.

14:02:01,369 INFO  [org.jboss.modules] (main) JBoss Modules version 1.2.0.Final-redhat-1

14:02:02,072 INFO  [org.jboss.msc] (main) JBoss MSC version 1.0.4.GA-redhat-1

14:02:02,379 INFO  [org.jboss.as] (MSC service thread 1-2) JBAS015899: JBoss EAP 6.1.0.GA (AS 7.2.0.Final-redhat-8) starting

14:02:05,629 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 9) JBAS014612: Operation ("add") failed - address: ([

    ("subsystem" => "logging"),

    ("console-handler" => "CONSOLE")

]): java.lang.ClassCastException: org.jboss.logmanager.PropertyConfigurator cannot be cast to org.jboss.as.logging.logmanager.ConfigurationPersistence

        at org.jboss.as.logging.logmanager.ConfigurationPersistence.getOrCreateConfigurationPersistence(ConfigurationPersistence.java:93)

        at org.jboss.as.logging.logmanager.ConfigurationPersistence.getOrCreateConfigurationPersistence(ConfigurationPersistence.java:81)

        at org.jboss.as.logging.LoggingOperations$LoggingOperationStepHandler.execute(LoggingOperations.java:154)

        at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:440) [jboss-as-controller-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]

        at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:322) [jboss-as-controller-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]

        at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:229) [jboss-as-controller-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]

        at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:224) [jboss-as-controller-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]

        at org.jboss.as.controller.ParallelBootOperationStepHandler$ParallelBootTask.run(ParallelBootOperationStepHandler.java:334) [jboss-as-controller-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]

        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_04]

        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_04]

        at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_04]

        at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.0.Final-redhat-1.jar:2.1.0.Final-redhat-1]

14:02:05,698 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) "JBAS014784: Failed executing subsystem logging boot operations"

14:02:05,710 FATAL [org.jboss.as.server] (Controller Boot Thread) JBAS015957: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.

14:02:05,736 INFO  [org.jboss.as] (MSC service thread 1-2) JBAS015950: JBoss EAP 6.1.0.GA (AS 7.2.0.Final-redhat-8) stopped in 16ms

[Arun_Dasetty]

Hi Brad,

We are afraid to inform that we might be hitting a known jboss bug specific to particular jboss version, but we would like to go through few details and try few changes in your test environment before we see if we are hitting bug here, Hope the plan of action is fine with you:

https://bugzilla.redhat.com/show_bug.cgi?id=969530
https://bugzilla.redhat.com/show_bug.cgi?id=969530
https://issues.jboss.org/browse/WFLY-895

We understood that the issue is not happening with older agent version and hence would like to try the following changes:

- Open app-agent-config.xml file in edit view and disable the service with name DynamicServiceManager, set enabled=false in xml element which is by default true and save the changes and see how it goes with jvm restart

- If issue still persists , do the following changes:

   a) update the modules system property in startup jvm args as follows:
 -Djboss.modules.system.pkgs=org.jboss.byteman,com.singularity
  b) remove the jvm arg -Djava.util.logging.manager if exists
  c) remove log4j-1.2.x.jar jar in -Xbootclasspath if exists as part of startup jboss arg and save the changes and see how it goes with restart

If the above information does not help, provide the following to assist you further:

- latest console stacktrace from jboss console including command used to start jboss server

- jboss startup scripts file 

- zipped version of <agent_install_dir>/logs path

Regards,

Arun

[CommunityUser]

Could you please provide your ample inputs to me. I am also facing same issue during configuration