[
https://issues.jboss.org/browse/WFCORE-2223?page=com.atlassian.jira.plugi...
]
Josef Cacek updated WFCORE-2223:
--------------------------------
Steps to Reproduce:
{code}
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
{code}
The same behavior is if you provide the commands in a script and use {{--file=}} JBoss CLI
argument.
was:
{code}
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.
Setting JBOSS_MODULEPATH is lost for second start of embed-server
-----------------------------------------------------------------
Key: WFCORE-2223
URL:
https://issues.jboss.org/browse/WFCORE-2223
Project: WildFly Core
Issue Type: Bug
Components: CLI, Modules
Reporter: Josef Cacek
Assignee: David Lloyd
Priority: Critical
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:
{code}
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
{code}
Using the {{JBOSS_MODULEPATH}} environment variable is documented in
https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-appli...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)