1 2 Previous Next 20 Replies Latest reply: Jun 23, 2013 12:51 AM by Shaler Wells RSS

Cannot start AS 7.1 Final LogManager error

Tanya Ruttenberg Expert

I just installed AS 7.1 today and am using eclipse to start it.  I updated my JBoss Tools before doing any of this.

 

When I try to start AS 7.1 I got this IllegalStateException

 

The LogManager was not properly installed (you must set the "java.util.logging.manager" system property to "org.jboss.logmanager.LogManager")

 

In the launch configuration, under VM arguments I added

 

"-Djava.util.logging.manager=org.jboss.logmanager.LogManager"

 

And now I get java.lang.ClassNotFoundException: org.jboss.logmanager.LogManager

 

How to fix this?

 

TDR

  • 1. Re: Cannot start AS 7.1 Final LogManager error
    jaikiran pai Master

    What path is JBoss and Java installed in? Please post the exact console logs.

  • 2. Re: Cannot start AS 7.1 Final LogManager error
    Tanya Ruttenberg Expert

    Yes, I saw a reference in the forums about a space in the path.  There isn't one. It's installed here

     

    D:/Development2/jboss-as-7.1.0.CR1b

     

    TDR

     

  • 3. Re: Cannot start AS 7.1 Final LogManager error
    Tanya Ruttenberg Expert

    Oh, but Java is. It's somewhere down in "Program Files".  can that make a difference?

     

    I will change it and see how far that gets me.

     

    thanks for the prompt reply BTW.

     

    TDR

  • 4. Re: Cannot start AS 7.1 Final LogManager error
    Tanya Ruttenberg Expert

    Still not working.  Here is the full stack trace.

     

    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:306)
    at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
    at java.util.logging.LogManager$1.run(LogManager.java:166)
    at java.security.AccessController.doPrivileged(Native Method)
    at java.util.logging.LogManager.<clinit>(LogManager.java:156)
    at java.util.logging.Logger.getLogger(Logger.java:287)
    at com.sun.jmx.remote.util.ClassLogger.<init>(ClassLogger.java:37)
    at javax.management.NotificationBroadcasterSupport.<clinit>(NotificationBroadcasterSupport.java:335)
    at javax.management.MBeanServerDelegate.<init>(MBeanServerDelegate.java:58)
    at com.sun.jmx.mbeanserver.MBeanServerDelegateImpl.<init>(MBeanServerDelegateImpl.java:82)
    at com.sun.jmx.mbeanserver.JmxMBeanServer.newMBeanServerDelegate(JmxMBeanServer.java:1326)
    at javax.management.MBeanServerBuilder.newMBeanServerDelegate(MBeanServerBuilder.java:49)
    at javax.management.MBeanServerFactory.newMBeanServer(MBeanServerFactory.java:302)
    at javax.management.MBeanServerFactory.createMBeanServer(MBeanServerFactory.java:213)
    at javax.management.MBeanServerFactory.createMBeanServer(MBeanServerFactory.java:174)
    at sun.management.ManagementFactory.createPlatformMBeanServer(ManagementFactory.java:302)
    at java.lang.management.ManagementFactory.getPlatformMBeanServer(ManagementFactory.java:504)
    at org.jboss.modules.ModuleLoader$RealMBeanReg$1.run(ModuleLoader.java:835)
    at org.jboss.modules.ModuleLoader$RealMBeanReg$1.run(ModuleLoader.java:833)
    at java.security.AccessController.doPrivileged(Native Method)
    at org.jboss.modules.ModuleLoader$RealMBeanReg.<init>(ModuleLoader.java:833)
    at org.jboss.modules.ModuleLoader$TempMBeanReg.installReal(ModuleLoader.java:817)
    at org.jboss.modules.ModuleLoader.installMBeanServer(ModuleLoader.java:192)
    at org.jboss.modules.Main.main(Main.java:312)
    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: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: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

     

     

    And I am including a picture that shows how I have set java.util.logging.manager. It's tiny, but I think you can see it.  What the heck am I doing wrong?

     

    eclipse.png

  • 5. Re: Cannot start AS 7.1 Final LogManager error
    jaikiran pai Master

    So you are trying to start this from an IDE? Try starting it outside of the IDE using the standalone.bat and see if that works. If it doesn't, then post the entire logs that you see on the console (including the echo statements).

  • 6. Re: Cannot start AS 7.1 Final LogManager error
    Tanya Ruttenberg Expert

    Yes, from within eclipse. I prefer that because I like the integration between my code and the server. I especially like to be able to step through code in the debugger.

     

    Anyhow from the command line the server starts beautifully (and quickly!).

     

    Can I really not start this from within eclipse?  That's disappointing.

     

    TDR

  • 7. Re: Cannot start AS 7.1 Final LogManager error
    jaikiran pai Master

    Moved to JBoss Tools forum.

  • 8. Re: Cannot start AS 7.1 Final LogManager error
    Max Rydahl Andersen Master

    AS7.1 snapshots have had problems the last week or so.

     

    One being AS7.1 not able to handle spaces - that got fixed today afaik

    Another about AS7.1 failing on -logmodule. That got fixed a few days ago.

     

    My last downloaded AS7.1 snapshot works fine for me on OSX so would be good to hear which exact build version of AS7.1 you are tryingout ?

  • 9. Re: Cannot start AS 7.1 Final LogManager error
    Tanya Ruttenberg Expert

    7.1.0CR1b

     

    I just downloaded it a couple of hours ago

  • 10. Re: Cannot start AS 7.1 Final LogManager error
    Max Rydahl Andersen Master

    hmm - please open bug at https://jira.jboss.org/jira/browse/JBIDE with the details and we'll take a look.

     

    7.1.0CR1b definitely starts on osx, linux and at least *some* windows users so need to find what makes you "special"

  • 11. Re: Cannot start AS 7.1 Final LogManager error
    Tanya Ruttenberg Expert

    Before I open a bug I decided to straighten out my Jboss Tools installation.  I was updating from both the nightly build site and the stable jboss tools site and things got a little confused. So I figured out finally how to install a stable recent version from Eclipse marketplace (yay) and I still have the problem (boo).

     

    If I understand correctly, there are 2 ways to define a log manager. You can either give a "program argument" like this (remember I'm doing this from within eclipse)

     

        -logmodule org.jboss.logmanager

     

    OR define it in the "VM arguments"

     

         -Djava.util.logging.manager=org.jboss.logmanager.LogManager

     

    I have tried every combination of those two things, ie neither, just -logmodule, just -Djava.util.logging.manager, both together.  ?

     

    And yet the problem persists.  I would really love to be able to manage my server from within eclipse, but so far it's a no go.

    Any other ideas Max, et al?

     

    TDR

  • 12. Re: Cannot start AS 7.1 Final LogManager error
    Rob Cernich Master

    I ran into this myself a couple days ago.  Try the following:

     

    Open the launch configuration for the server definition.

    Add: -logmodule org.jboss.logmanager to the program arguments before org.jboss.as.standalone

     

    Hope that helps,

    Rob

  • 13. Re: Cannot start AS 7.1 Final LogManager error
    Max Rydahl Andersen Master

    Yes - what Rob said.

     

    Tanya - after your email I checked and yes -logmodule org.jboss.logmanager is the right thing to put there but only in program arguments not vm arguments.

  • 14. Re: Cannot start AS 7.1 Final LogManager error
    Tanya Ruttenberg Expert

    I actually did play around with the order of the program arguments, but apparently not enough.  What Rob said is exactly what worked.

     

    FTR

     

    -mp "D:/Development2/jboss-as-7.1.0.CR1b/modules" -jaxpmodule javax.xml.jaxp-provider -logmodule org.jboss.logmanager org.jboss.as.standalone -b 0.0.0.0 --server-config=standalone.xml

     

    Thanks Rob and Max!

1 2 Previous Next