[jboss-jira] [JBoss JIRA] (AS7-1859) AS won't boot with sun jmx enabled

David Lloyd (JIRA) jira-events at lists.jboss.org
Wed Jun 5 08:48:55 EDT 2013


    [ https://issues.jboss.org/browse/AS7-1859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12779494#comment-12779494 ] 

David Lloyd commented on AS7-1859:
----------------------------------

Using the JMXRemote agent will never be supported unless they fix the log manager initialization order problem, which they will likely never do.  It might be possible to manually instantiate it somehow though after the server is booted.
                
> AS won't boot with sun jmx enabled
> ----------------------------------
>
>                 Key: AS7-1859
>                 URL: https://issues.jboss.org/browse/AS7-1859
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: Logging
>    Affects Versions: 7.1.0.Alpha1
>         Environment: sun jdk6 windows 7 as-7.1.0.Alpha1
>            Reporter: Dan Hanley
>            Assignee: David Lloyd
>
> This appears to be a regression to https://issues.jboss.org/browse/JBAS-7427 in AS7.1
> > set JAVA_OPTS=%JAVA_OPTS%  -Dcom.sun.management.jmxremote -Djava.util.logging.manager=org.jboss.logmanager.LogManager 
> > standalone.bat
> ===============================================================================
>   JBoss Bootstrap Environment
>   JBOSS_HOME: c:\jboss-as-7.1.0.Alpha1-SNAPSHOT
>   JAVA: C:\Program Files\Java\jdk1.6.0_22\bin\java
>   JAVA_OPTS: -Dprogram.name=standalone.bat -XX:+PrintGCDetails -XX:+PrintGCTimeStamps -XX:+PrintTenuringDistribution -XX:+UseParallelGC -XX:PermSize=6g -XX:MaxPermSize=6g -Xms512m
> -Xmx4g -Xss256k -Dhornetq.server-id=119 -Dsqs.queue.name=danQ -Duser.timezone=gmt -Djava.net.preferIPv4Stack=true -Djms.server=193.131.98.79 -Djboss.bind.address=193.131.98.79 -Djb
> oss.partition.name=dan-pc -Djboss.partition.udpGroup=79 -Dpublic.firewall.address=dan-pc -Xrunjdwp:transport=dt_socket,address=8788,server=y,suspend=n   -Dcom.sun.management.jmxrem
> ote -Djava.util.logging.manager=org.jboss.logmanager.LogManager -Dorg.jboss.logging.Logger.pluginClass=org.jboss.logging.logmanager.LoggerPluginImpl -server
> ===============================================================================
> Listening for transport dt_socket at address: 8788
> Could not load Logmanager "org.jboss.logmanager.LogManager"
> java.lang.ClassNotFoundException: org.jboss.logmanager.LogManager
>         at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
>         at java.security.AccessController.doPrivileged(Native Method)
>         at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
>         at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
>         at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
>         at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
>         at java.util.logging.LogManager$1.run(LogManager.java:168)
>         at java.security.AccessController.doPrivileged(Native Method)
>         at java.util.logging.LogManager.<clinit>(LogManager.java:158)
>         at java.util.logging.Logger.getLogger(Logger.java:273)
>         at sun.management.snmp.util.MibLogger.<init>(MibLogger.java:57)
>         at sun.management.snmp.util.MibLogger.<init>(MibLogger.java:42)
>         at sun.management.jmxremote.ConnectorBootstrap.<clinit>(ConnectorBootstrap.java:760)
>         at sun.management.Agent.startAgent(Agent.java:135)
>         at sun.management.Agent.startAgent(Agent.java:239)
> 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:81)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:597)
>         at org.jboss.modules.Module.run(Module.java:270)
>         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.LogMana
> ger")
>         at org.jboss.logmanager.Logger.getLogger(Logger.java:60)
>         at org.jboss.logmanager.log4j.BridgeRepositorySelector.<clinit>(BridgeRepositorySelector.java:42)
>         ... 7 more
> Heap
>  PSYoungGen      total 152896K, used 23619K [0x00000002aaaa0000, 0x00000002b5540000, 0x00000002ffff0000)
>   eden space 131072K, 18% used [0x00000002aaaa0000,0x00000002ac1b0f30,0x00000002b2aa0000)
>   from space 21824K, 0% used [0x00000002b3ff0000,0x00000002b3ff0000,0x00000002b5540000)
>   to   space 21824K, 0% used [0x00000002b2aa0000,0x00000002b2aa0000,0x00000002b3ff0000)
>  PSOldGen        total 349568K, used 0K [0x00000001ffff0000, 0x0000000215550000, 0x00000002aaaa0000)
>   object space 349568K, 0% used [0x00000001ffff0000,0x00000001ffff0000,0x0000000215550000)
>  PSPermGen       total 6291456K, used 10763K [0x000000007fff0000, 0x00000001ffff0000, 0x00000001ffff0000)
>   object space 6291456K, 0% used [0x000000007fff0000,0x0000000080a72d30,0x00000001ffff0000)
> Press any key to continue . . .

--
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


More information about the jboss-jira mailing list