[jboss-jira] [JBoss JIRA] Commented: (AS7-1547) Problem starting jboss 7 with Java Service Wrapper

[Shai Levi (JIRA)]

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

Shai Levi commented on AS7-1547:
--------------------------------

I had the same issue and I have contacted TanukiSoftware support and they responded with this configuration which ended up working perfectly for me:



> have you tried the following setting:
>
> wrapper.java.mainclass=org.tanukisoftware.wrapper.WrapperJarApp
>
> wrapper.java.classpath.1=%JBOSS_HOME%/lib/wrapper.jar
> wrapper.java.classpath.2=%JBOSS_HOME%/*.jar
>
> wrapper.java.library.path.1=../lib
>
> wrapper.java.additional.1=-XX:MaxPermSize=512m
> wrapper.java.additional.2=-Dorg.jboss.resolver.warning=true
> wrapper.java.additional.3=-Dsun.rmi.dgc.client.gcInterval=3600000
> wrapper.java.additional.4=-Dsun.rmi.dgc.server.gcInterval=3600000
> wrapper.java.additional.5=-Djboss.modules.system.pkgs=org.jboss.byteman
> wrapper.java.additional.6=-Dorg.tanukisoftware.wrapper.WrapperManager.mbean=false
> wrapper.java.additional.7=-Dlogging.configuration=file:%JBOSS_HOME%/standalone/configuration/logging.properties
>
> wrapper.java.additional.10=-Djava.util.logging.manager=org.jboss.logmanager.LogManager
> wrapper.java.additional.11=-Dorg.jboss.logging.Logger.pluginClass=org.jboss.logging.logmanager.LoggerPluginImpl
>
> # Application parameters.  Add parameters as needed starting from 1 wrapper.app.parameter.1=../jboss-modules.jar
> wrapper.app.parameter.2=-mp
> wrapper.app.parameter.3=%JBOSS_HOME%/modules
> wrapper.app.parameter.4=-logmodule
> wrapper.app.parameter.5=org.jboss.logmanager
> wrapper.app.parameter.6=-jaxpmodule
> wrapper.app.parameter.7=javax.xml.jaxp-provider
> wrapper.app.parameter.8=org.jboss.as.standalone
> wrapper.app.parameter.9=-Djboss.home.dir=%JBOSS_HOME%

> 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: David Lloyd
>             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