[
https://issues.jboss.org/browse/WFLY-895?page=com.atlassian.jira.plugin.s...
]
Juliana Louback edited comment on WFLY-895 at 11/14/13 9:32 AM:
----------------------------------------------------------------
As most of the comments suggest (particularly those by [~dmlloyd]), the java agent issue
lies with the log manager being used. To fix this problem using the jmxetric agent for
Ganglia (which also caused a JBoss crash), I commented out all the logging in jmxetric.
(See branch
https://github.com/JLouback/jmxetric/tree/logbranch)
After this, JBoss ran without an issue. I didn't perform very sophisticated tests:
simply ran JBoss with the original jmxetric jar, observed the crash, then ran it again
with the new jar (logging having been removed).
was (Author: jlouback):
As most of the comments suggest (particularly those by [~dmlloyd]), the java agent
issue lies with the log manager being used. To fix this problem using the jmxetric agent
for Ganglia (which also caused a JBoss crash), I commented out all the logging in
jmxetric. (See branch
https://github.com/JLouback/jmxetric/tree/logbranch)
After this, JBoss ran without an issue. I didn't perform very sophisticated tests:
simply ran JBoss with the original jmxetric jar, observed the crash, then ran it again
with the new jar without logging in jmxetric.
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:
=========================================================================
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
--
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