[jboss-jira] [JBoss JIRA] Commented: (JBAS-7427) AS won't boot with sun jmx enabled
David Lloyd (JIRA)
jira-events at lists.jboss.org
Wed Nov 4 12:35:05 EST 2009
[ https://jira.jboss.org/jira/browse/JBAS-7427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12493146#action_12493146 ]
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?
> AS won't boot with sun jmx enabled
> ----------------------------------
>
> Key: JBAS-7427
> URL: https://jira.jboss.org/jira/browse/JBAS-7427
> Project: JBoss Application Server
> 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: JBossAS-6.0.0.Alpha1
>
>
> [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.
-
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
More information about the jboss-jira
mailing list