Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-19879

[GSS](7.3.z) EAP Pod fails to start when env JBOSS_MODULEPATH=${JBOSS_HOME}/modules:${HOME} is set

    Details

    • Type: Bug
    • Status: New (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 7.3.1.GA
    • Fix Version/s: None
    • Component/s: OpenShift
    • Labels:
      None
    • Target Release:
    • Steps to Reproduce:
      Hide

      $ oc new-project test
      $ oc new-app --template eap73-basic-s2i -p APPLICATION_NAME=helloworld -p SOURCE_REPOSITORY_URL=https://github.com/jboss-developer/jboss-eap-quickstarts.git -p CONTEXT_DIR=helloworld -p SOURCE_REPOSITORY_REF=openshift
      $ oc set env dc/helloworld JBOSS_MODULEPATH=${JBOSS_HOME}/modules:${HOME}

      $ oc logs -f helloworld-3-mvv5z

      INFO Configuring JGroups cluster traffic encryption protocol to SYM_ENCRYPT.
      WARN Detected missing JGroups encryption configuration, the communication within the cluster WILL NOT be encrypted.
      INFO Configuring JGroups discovery protocol to dns.DNS_PING
      INFO Using PicketBox SSL configuration.
      INFO Access log is disabled, ignoring configuration.
      WARN Configuration of an embedded messaging broker within the appserver is enabled but is not recommended. Support for such a configuration will be removed in a future release.
      WARN If you are not configuring messaging destinations, to disable configuring an embedded messaging broker set the DISABLE_EMBEDDED_JMS_BROKER environment variable to true.
      INFO Configuring the server using embedded server
      INFO Duration: 347 milliseconds
      ERROR Error applying /tmp/cli-configuration-script-1594252654.cli CLI script.
      org.jboss.modules.ModuleNotFoundException: org.jboss.as.cli
      	at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:297)
      	at org.jboss.modules.Main.main(Main.java:371)
      
      Show
      $ oc new-project test $ oc new-app --template eap73-basic-s2i -p APPLICATION_NAME=helloworld -p SOURCE_REPOSITORY_URL= https://github.com/jboss-developer/jboss-eap-quickstarts.git -p CONTEXT_DIR=helloworld -p SOURCE_REPOSITORY_REF=openshift $ oc set env dc/helloworld JBOSS_MODULEPATH=${JBOSS_HOME}/modules:${HOME} $ oc logs -f helloworld-3-mvv5z INFO Configuring JGroups cluster traffic encryption protocol to SYM_ENCRYPT. WARN Detected missing JGroups encryption configuration, the communication within the cluster WILL NOT be encrypted. INFO Configuring JGroups discovery protocol to dns.DNS_PING INFO Using PicketBox SSL configuration. INFO Access log is disabled, ignoring configuration. WARN Configuration of an embedded messaging broker within the appserver is enabled but is not recommended. Support for such a configuration will be removed in a future release. WARN If you are not configuring messaging destinations, to disable configuring an embedded messaging broker set the DISABLE_EMBEDDED_JMS_BROKER environment variable to true. INFO Configuring the server using embedded server INFO Duration: 347 milliseconds ERROR Error applying /tmp/cli-configuration-script-1594252654.cli CLI script. org.jboss.modules.ModuleNotFoundException: org.jboss.as.cli at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:297) at org.jboss.modules.Main.main(Main.java:371)
    • Workaround Description:
      Hide

      There are several workarounds.

      1. Adding a module by S2I build instead of a custom module path as explained in the document 9.13.1.1. Custom Modules
      2. Excluding bash variables in JBOSS_MODULEPATH like JBOSS_MODULEPATH=/opt/jboss/modules:/home/jboss
      3. Set environment variable CONFIG_IS_FINAL=true to prevent calling jboss-cli.sh in EAP container startup scripts.
      Show
      There are several workarounds. Adding a module by S2I build instead of a custom module path as explained in the document 9.13.1.1. Custom Modules Excluding bash variables in JBOSS_MODULEPATH like JBOSS_MODULEPATH=/opt/jboss/modules:/home/jboss Set environment variable CONFIG_IS_FINAL=true to prevent calling jboss-cli.sh in EAP container startup scripts.

      Description

      Since JBoss EAP 7.3 for OpenShift, if environment variable JBOSS_MODULEPATH=${JBOSS_HOME}/modules:${HOME} which contains bash variable is set via DeploymentConfig, EAP Pod fails to start with the following messages:

      INFO Duration: 347 milliseconds
      ERROR Error applying /tmp/cli-configuration-script-1594252654.cli CLI script.
      org.jboss.modules.ModuleNotFoundException: org.jboss.as.cli
      	at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:297)
      	at org.jboss.modules.Main.main(Main.java:371)
      

      This issue does not occur on JBoss EAP 7.2 container.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                istudens Ivo Studensky
                Reporter:
                norito.agetsuma Norito Agetsuma
              • Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated: