Application Server 7
  1. Application Server 7
  2. AS7-1547

Problem starting jboss 7 with Java Service Wrapper

    Details

    • Type: Bug Bug
    • Status: Closed (View Workflow)
    • Priority: Major Major
    • Resolution: Out of Date Out of Date
    • Affects Version/s: 7.0.0.Final
    • Fix Version/s: Awaiting Volunteers
    • Component/s: Logging
    • Labels:
      None
    • Environment:
      Red Hat, Windows 7
    • Workaround Description:
      Hide

      No work around seems to exist.

      Show
      No work around seems to exist.
    • Similar Issues:
      Show 10 results 

      Description

      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.

        Gliffy Diagrams

          Activity

          Hide
          Shai Levi added a comment -

          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%

          Show
          Shai Levi added a comment - 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%
          Hide
          andrei povodyrev added a comment -

          This line does the job
          wrapper.java.additional.10=-Dorg.tanukisoftware.wrapper.WrapperManager.mbean=false
          I guess that the disabled code is the one who gets access to LogManager
          before Jboss does. This is a workaround, though I still believe this is a jboss bug

          Shai, thank you for the reference

          Show
          andrei povodyrev added a comment - This line does the job wrapper.java.additional.10=-Dorg.tanukisoftware.wrapper.WrapperManager.mbean=false I guess that the disabled code is the one who gets access to LogManager before Jboss does. This is a workaround, though I still believe this is a jboss bug Shai, thank you for the reference
          Hide
          James Baxter added a comment -

          Looks like a similar issue arises when connecting the Chronon recording agent... http://community.chrononsystems.com/chronon_systems/topics/cannot_record_jboss_as7_via_ide#reply_6635782

          Show
          James Baxter added a comment - Looks like a similar issue arises when connecting the Chronon recording agent... http://community.chrononsystems.com/chronon_systems/topics/cannot_record_jboss_as7_via_ide#reply_6635782
          Hide
          James Perkins added a comment -

          Please re-open if this is still an issue.

          Show
          James Perkins added a comment - Please re-open if this is still an issue.
          Hide
          Radai Rosenblatt added a comment -

          we're having this exact issue using jboss 7.1.3.Final
          as stated above it is directly linked to service wrapper jmx initialization interacting with jboss logging

          Show
          Radai Rosenblatt added a comment - we're having this exact issue using jboss 7.1.3.Final as stated above it is directly linked to service wrapper jmx initialization interacting with jboss logging

            People

            • Assignee:
              James Perkins
              Reporter:
              andrei povodyrev
            • Votes:
              1 Vote for this issue
              Watchers:
              9 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development