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

Setting JBOSS_MODULEPATH is lost for second start of embed-server

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Critical Critical
    • 7.1.0.DR12
    • 7.0.4.GA, 7.1.0.DR10
    • Server
    • None
    • Hide 
      unzip -q jboss-eap-7.0.0.zip
cp -r jboss-eap-7.0/ jboss-eap-7.0-no-modules
rm -rf jboss-eap-7.0-no-modules/modules/
export JBOSS_MODULEPATH=`pwd`/jboss-eap-7.0/modules
jboss-eap-7.0-no-modules/bin/jboss-cli.sh << EOT
embed-server
stop-embedded-server
embed-server
stop-embedded-server
EOT

      The same behavior is if you provide the commands in a script and use --file= JBoss CLI argument.

      Show
      unzip -q jboss-eap-7.0.0.zip cp -r jboss-eap-7.0/ jboss-eap-7.0-no-modules rm -rf jboss-eap-7.0-no-modules/modules/ export JBOSS_MODULEPATH=`pwd`/jboss-eap-7.0/modules jboss-eap-7.0-no-modules/bin/jboss-cli.sh << EOT embed-server stop-embedded-server embed-server stop-embedded-server EOT The same behavior is if you provide the commands in a script and use --file= JBoss CLI argument.

      When embed-server command is used more times in the CLI and a custom JBOSS_MODULEPATH is configured, then only the first server start uses the correct module path.
      The subsequent `embed-server` call results in error:

      Cannot start embedded server: WFLYEMB0022: Cannot invoke 'start' on embedded process: WFLYSRV0118: Determined modules directory does not exist: /tmp/jboss-eap-7.0-no-modules/modules

      Using the JBOSS_MODULEPATH environment variable is documented in https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/7.0/single/configuration-guide/#define_an_external_jboss_eap_module_directory

              bstansbe@redhat.com Brian Stansberry
              josef.cacek@gmail.com Josef Cacek (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: