From mark.ambrose at bluemedora.com Tue Nov 13 18:37:23 2018 From: mark.ambrose at bluemedora.com (Mark Ambrose) Date: Tue, 13 Nov 2018 18:37:23 -0500 Subject: [Hawkular-dev] logging in java agents is not trivial in WildFly / EAP Message-ID: >>> ... this means problems still need to be overcome when >>> putting java agents in host controllers for EAP 7.0 domain mode. >>> Is a solution to these problems for when putting java agents in host controllers for EAP 7.0 domain mode known? ... [Host Controller] 16:16:33,937 INFO [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0023: Starting server TestServer1a 16:16:33,968 INFO [org.jboss.as.process.Server:TestServer1a.status] (ProcessController-threads - 3) WFLYPC0018: Starting process 'Server:TestServer1a' [Server:TestServer1a] Could not load Logmanager "org.jboss.logmanager.LogManager" [Server:TestServer1a] java.lang.ClassNotFoundException: org.jboss.logmanager.LogManager [Server:TestServer1a] at java.net.URLClassLoader.findClass(URLClassLoader.java:382) ... Thanks, Mark Ambrose -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20181113/1b3653c5/attachment.html From jmartisk at redhat.com Wed Nov 14 05:33:46 2018 From: jmartisk at redhat.com (=?UTF-8?Q?Jan_Marti=C5=A1ka?=) Date: Wed, 14 Nov 2018 11:33:46 +0100 Subject: [Hawkular-dev] logging in java agents is not trivial in WildFly / EAP In-Reply-To: References: Message-ID: >From the log you attached it seems you are adding the agent to a managed server, not the host controller. Can you try adding these three settings to the managed servers' JVM configuration? AFAIK this needs to be done for the boot class loader to be able to access the logmanager... I know especially the second one is ugly but I'm not aware of a better solution at the moment -Djboss.modules.system.pkgs=org.jboss.byteman,org.jboss.logmanager -Xbootclasspath/a:modules/system/layers/base/org/jboss/logmanager/main/jboss-logmanager-2.0.7.Final-redhat-1.jar -Djava.util.logging.manager=org.jboss.logmanager.LogManager Jan On Wed, Nov 14, 2018 at 12:38 AM Mark Ambrose wrote: > >>> ... this means problems still need to be overcome when > >>> putting java agents in host controllers for EAP 7.0 domain mode. > >>> > > Is a solution to these problems for when putting java agents in host controllers for EAP 7.0 domain mode known? > > ... > [Host Controller] 16:16:33,937 INFO [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0023: Starting server TestServer1a > 16:16:33,968 INFO [org.jboss.as.process.Server:TestServer1a.status] (ProcessController-threads - 3) WFLYPC0018: Starting process 'Server:TestServer1a' > [Server:TestServer1a] Could not load Logmanager "org.jboss.logmanager.LogManager" > [Server:TestServer1a] java.lang.ClassNotFoundException: org.jboss.logmanager.LogManager > [Server:TestServer1a] at java.net.URLClassLoader.findClass(URLClassLoader.java:382) > ... > > Thanks, > Mark Ambrose > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20181114/5ec06ad0/attachment.html