Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error when trying to use with JBoss 7.1 #4

Open
GoogleCodeExporter opened this issue Mar 22, 2015 · 3 comments
Open

Error when trying to use with JBoss 7.1 #4

GoogleCodeExporter opened this issue Mar 22, 2015 · 3 comments

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?
Just try to run JBoss with loosejar agent 

What version of the product are you using? On what operating system?
JBoss 7.1.1 on Ubuntu 12.10

Please provide any additional information below.
Output:

=========================================================================

  JBoss Bootstrap Environment

  JBOSS_HOME: /workspace/jboss7

  JAVA: java

  JAVA_OPTS:  -server -XX:+UseCompressedOops -XX:+TieredCompilation -javaagent:/home/gk/Downloads/loosejar-1.0.1.jar -Xms1024m -Xmx2048m -XX:NewRatio=3 -XX:MinHeapFreeRatio=20 -XX:PermSize=256m -XX:MaxPermSize=320m -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 -Djboss.server.default.config=standalone-full.xml -Dfile.encoding=UTF-8 -Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n 
=========================================================================

[loosejar]: loosejar analysis is registered to run on JVM shutdown.
[loosejar]: Registering loosejar as a JMX service...
[loosejar]: Registered loosejar as a JMX service: 
[com.googlecode.loosejar:type=LooseJarMBean]

Listening for transport dt_socket at address: 8787
WARNING: Failed to load the specified log manager class 
org.jboss.logmanager.LogManager
Exception in thread "main" java.lang.ExceptionInInitializerError
    at org.jboss.as.server.Main.main(Main.java:73)
    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:606)
    at org.jboss.modules.Module.run(Module.java:260)
    at org.jboss.modules.Main.main(Main.java:291)
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:61)
    at org.jboss.logmanager.log4j.BridgeRepositorySelector.<clinit>(BridgeRepositorySelector.java:42)
    ... 7 more
[loosejar]: Found 1516 classes loaded in the JVM.
[loosejar]: Found 10 various ClassLoader(s) inside the JVM.
[loosejar]: Summary for [sun.misc.Launcher$AppClassLoader] classloader:

    Jar: /workspace/jboss7/jboss-modules.jar
    Utilization: 72,15% - loaded 114 of 158 classes.

When using without loosejar everything is ok. Also setting property mentioned 
in error message does not help.

Original issue reported on code.google.com by kaczmarc...@mail.com on 12 May 2014 at 7:40

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant