Status: Closed (View Workflow)
Resolution: Out of Date
Affects Version/s: 7.0.0.Final
Fix Version/s: Awaiting Volunteers
Environment:Red Hat, Windows 7
Similar Issues:Show 10 results
AS7-2533 Problem with Classloading Isolation in JBoss 7.0.1 AS7-4348 deployment fails on jboss 7 with generic message. AS7-2470 Alias java:jboss/TransactionManager to java:/TransactionManager AS7-2769 Arquillian Managed container always using java command to start the container regardless of JAVA_HOME setting or javaHome property in arquillian.xml AS7-961 AS 7 standalone instance doesn't shutdown AS7-3762 Unable to start jBoss AS 7 in standalone AS7-333 Context is lost if a service fails to start for a 'random' reason AS7-3141 Problem with JBoss 7.1.0 and oracle datasource configuration AS7-234 Cannot build JBoss AS 7 using OpenJDK AS7-3684 AS7.1 can't start on windows
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")
wrapper-windows-x86-64-3.5.10-st (Java Service Wrapper win 64 distribution)
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.