[jboss-jira] [JBoss JIRA] Commented: (JBAS-7427) AS won't boot with sun jmx enabled

[Paul Sideleau (JIRA)]

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

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? 



> AS won't boot with sun jmx enabled
> ----------------------------------
>
>                 Key: JBAS-7427
>                 URL: https://issues.jboss.org/browse/JBAS-7427
>             Project: Legacy JBoss Application Server 6 
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Logging
>         Environment: sun jdk6, fedora, AS trunk r96005
>            Reporter: Jonathan Halliday
>            Assignee: David Lloyd
>             Fix For: 6.0.0.M2
>
>
> [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"
> [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.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
> =========================================================================
> Failed to initalize plugin: org.jboss.logging.logmanager.LoggerPluginImpl at 214a55f2, 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")
> ...
> Failed to initalize plugin: org.jboss.aop.util.logging.SystemOutLoggerPlugin at 5c1ae90c, cause: java.lang.AbstractMethodError

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira