[ https://jira.jboss.org/jira/browse/JBAS-7427?page=com.atlassian.jira.plug... ] Jonathan Halliday commented on JBAS-7427: ----------------------------------------- [jhalli jboss-6.0.0-SNAPSHOT]$ export JAVA_OPTS="-Dcom.sun.management.jmxremote.port=12345 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false -Djava.util.logging.manager=org.jboss.logmanager.LogManager" [jhalli jboss-6.0.0-SNAPSHOT]$ bin/run.sh ========================================================================= JBoss Bootstrap Environment JBOSS_HOME: /home/jhalli/IdeaProjects/jboss/jbossas_trunk/build/output/jboss-6.0.0-SNAPSHOT JAVA: /usr/local/jdk1.6.0_16/bin/java JAVA_OPTS: -Dprogram.name=run.sh -server -Dcom.sun.management.jmxremote.port=12345 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false -Djava.util.logging.manager=org.jboss.logmanager.LogManager -Djava.net.preferIPv4Stack=true CLASSPATH: /home/jhalli/IdeaProjects/jboss/jbossas_trunk/build/output/jboss-6.0.0-SNAPSHOT/bin/run.jar:/usr/local/jdk1.6.0_16/lib/tools.jar ========================================================================= Could not load Logmanager "org.jboss.logmanager.LogManager" java.lang.ClassNotFoundException: org.jboss.logmanager.LogManager at java.net.URLClassLoader$1.run(URLClassLoader.java:200) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:188) at java.lang.ClassLoader.loadClass(ClassLoader.java:307) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301) at java.lang.ClassLoader.loadClass(ClassLoader.java:252) 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: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:127) at sun.management.Agent.startAgent(Agent.java:239) Failed to initalize plugin: org.jboss.aop.util.logging.SystemOutLoggerPlugin@2880cac9, cause: java.lang.AbstractMethodError -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBAS-7427?page=com.atlassian.jira.plug... ] David Lloyd commented on JBAS-7427: ----------------------------------- The underlying problem is that the Agent is started *before* main() if either -Dcom.sun.management.snmp or -Dcom.sun.management.jmxremote are set. Maybe the cleanest solution is to have a LazyLogManager which is in run.jar which lets another LogManager come along later on. It could even queue up messages, to a point, to give at least the illusion of having all messages from first boot onwards (even agent methods). Then in run.sh/run.bat we'd preconfigure the lazy logmanager as the JDK logmanager, and cram the real logmanager in there during bootstrap somehow? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBAS-7427?page=com.atlassian.jira.plug... ] David Lloyd resolved JBAS-7427. ------------------------------- Resolution: Done OK so I updated jboss-logmanager so there's no dep on common core. So you should be able to do this: JAVA_OPTS="-Dcom.sun.management.jmxremote.port=12345 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false -Djava.util.logging.manager=org.jboss.logmanager.LogManager -Dorg.jboss.logging.Logger.pluginClass=org.jboss.logging.logmanager.LoggerPluginImpl" sh bin/run.sh ...and things should work, at least as far as logging is concerned. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBAS-7427?page=com.atlassian.jira.plug... ] Jonathan Halliday reopened JBAS-7427: ------------------------------------- $ export JAVA_OPTS="-Dcom.sun.management.jmxremote.port=12345 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false -Djava.util.logging.manager=org.jboss.logmanager.LogManager -Dorg.jboss.logging.Logger.pluginClass=org.jboss.logging.logmanager.LoggerPluginImpl" $ bin/run.sh ========================================================================= JBoss Bootstrap Environment JBOSS_HOME: /home/jhalli/IdeaProjects/jboss/jbossas_trunk/build/target/jboss-6.0.0-SNAPSHOT JAVA: /usr/local/jdk1.6.0_17/bin/java JAVA_OPTS: -Dprogram.name=run.sh -server -Dcom.sun.management.jmxremote.port=12345 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false -Djava.util.logging.manager=org.jboss.logmanager.LogManager -Dorg.jboss.logging.Logger.pluginClass=org.jboss.logging.logmanager.LoggerPluginImpl -Djava.net.preferIPv4Stack=true CLASSPATH: /home/jhalli/IdeaProjects/jboss/jbossas_trunk/build/target/jboss-6.0.0-SNAPSHOT/bin/run.jar:/usr/local/jdk1.6.0_17/lib/tools.jar ========================================================================= Could not load Logmanager "org.jboss.logmanager.LogManager" java.lang.ClassNotFoundException: org.jboss.logmanager.LogManager at java.net.URLClassLoader$1.run(URLClassLoader.java:200) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:188) at java.lang.ClassLoader.loadClass(ClassLoader.java:303) 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: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: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:127) at sun.management.Agent.startAgent(Agent.java:239) Failed to initalize plugin: org.jboss.logging.logmanager.LoggerPluginImpl@58d9660d, cause: java.lang.IllegalStateException: The LogManager was not properly installed (you must set the "java.util.logging.manager" system property to "org.jboss.logmanager.LogManager") -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBAS-7427?page=com.atlassian.jira.plug... ] Jonathan Halliday commented on JBAS-7427: ----------------------------------------- Then the steps to do so need documenting, or it needs to live there by default. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBAS-7427?page=com.atlassian.jira.plugin.... ] Paul Sideleau commented on JBAS-7427: ------------------------------------- I believe an additional step is required. I had a related issue enabling the aspectj load time weaver as a java agent. It required me to setup the same logging configuration changes that were included in this ticket. While testing on windows, I noticed it creating a "${jboss.boot.server.log.dir}" directory for the boot.log file instead of placing it in the server's log directory. On one of our clustered linux servers, it was causing an error to triger:"${jboss.boot.server.log.dir}" is not a directory. I believe this is because all the systems properties have not been configured yet. I explicitly had to add -Djboss.boot.server.log.dir=/jboss-6.0.0.Final/server/default/log in addition to the parameters, -Djava.util.logging.manager=org.jboss.logmanager.LogManager -Dorg.jboss.logging.Logger.pluginClass=org.jboss.logging.logmanager.LoggerPluginImpl" This workaround will cause issues if you need to start up multiple jboss servers, such as "default" and "all". Is there a better approach for this? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira