[jboss-jira] [JBoss JIRA] Updated: (AS7-1547) Problem starting jboss 7 with Java Service Wrapper
David Lloyd (JIRA)
jira-events at lists.jboss.org
Mon Sep 26 14:04:29 EDT 2011
[ https://issues.jboss.org/browse/AS7-1547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Lloyd updated AS7-1547:
-----------------------------
Assignee: James Perkins (was: David Lloyd)
> Problem starting jboss 7 with Java Service Wrapper
> --------------------------------------------------
>
> Key: AS7-1547
> URL: https://issues.jboss.org/browse/AS7-1547
> Project: Application Server 7
> Issue Type: Bug
> Components: Logging
> Affects Versions: 7.0.0.Final
> Environment: Red Hat, Windows 7
> Reporter: andrei povodyrev
> Assignee: James Perkins
> Fix For: Open To Community
>
>
> Problem starting jboss 7 with Java Service Wrapper
> We tried to upgrade Java Service Wrapper (JSW) configuration from Jboss 5 to Jboss 7.
> Jboss fails to start with these messages
> WARNING: Failed to load the specified logmodule org.jboss.logmanager:main
> followed by IllegalStateException: The LogManager was not properly installed (you must set the "java.util.logging.manager" system property to "org.jboss.logmanager.LogManager")
> Software:
> Jboss-as-7.0.0-Final
> wrapper-windows-x86-64-3.5.10-st (Java Service Wrapper win 64 distribution)
> Issue:
> org.jboss.modules.Main generates the warning as LogManager is already initialized to java.util.logging.LogManager by the Wrapper.
> With jboss 7 org.jboss.logmanager.LogManager is required. Per LogManager design only one instance may exist in jvm.
> jboss 7 assume that it is the first in line to initialize java.util.logger.LogManager.
> Wrapper is the one who inits LogManager first (thus triggering primordial
> configuration initialization). Jboss then fails to start since it requiresits own logging implementation.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list