[
https://issues.jboss.org/browse/WFLY-895?page=com.atlassian.jira.plugin.s...
]
dpocock commented on WFLY-895:
------------------------------
Understood - jmxetric no longer does any logging, it just gives one line on stdout to
confirm it has loaded.
That is not the full story though - when the agent wants to interact with JMX, that causes
the JBoss JMX code to be invoked before it is really ready. Not only does that cause JMX
problems later (as in WFLY-3054), but the JBoss JMX code also tried to access the logger
at this early stage in the boot process, it can't find it on the classpath and so
startup fails.
The bootclasspath stuff helps the JBoss JMX code to survive the startup process but I
agree this is not a desirable way to go about it.
JBoss crashes when run with AspectJ java agent
----------------------------------------------
Key: WFLY-895
URL:
https://issues.jboss.org/browse/WFLY-895
Project: WildFly
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Server
Environment: OS X 10.7.2, Ubuntu 11.10
Reporter: Jack Lund
Assignee: David Lloyd
Labels: aspectj, load_time_weaving
When trying to start JBoss with the AspectJ java agent
(-javaagent:/path/aspectjweaver.jar) to enable load-time weaving, JBoss crashes with the
following stack trace in the logs:
{noformat}
=========================================================================
JBoss Bootstrap Environment
JBOSS_HOME: /home/jack/jboss-as-7.1.0.CR1b
JAVA: java
JAVA_OPTS: -server -javaagent:/home/jack/aspectjweaver.jar -Xms64m -Xmx512m
-XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true
-Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000
-Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true
=========================================================================
WARNING: Failed to load the specified logmodule org.jboss.logmanager:main
Exception in thread "main" java.lang.ExceptionInInitializerError
at org.jboss.as.server.Main.main(Main.java:92)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at org.jboss.modules.Module.run(Module.java:248)
at org.jboss.modules.Main.main(Main.java:313)
Caused by: java.lang.IllegalStateException: The LogManager was not properly installed
(you must set the "java.util.logging.manager" system property to
"org.jboss.logmanager.LogManager")
at org.jboss.logmanager.Logger.getLogger(Logger.java:60)
at
org.jboss.logmanager.log4j.BridgeRepositorySelector.<clinit>(BridgeRepositorySelector.java:42)
... 7 more
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira