[jboss-jira] [Red Hat JIRA] (WFCORE-5216) EAP Pod fails to start when env JBOSS_MODULEPATH=${JBOSS_HOME}/modules:${HOME} is set
[
https://issues.redhat.com/browse/WFCORE-5216?page=com.atlassian.jira.plug...
]
Davy Koravand commented on WFCORE-5216:
---------------------------------------
As an update, I checked my scenario with WildFly 22 beta and the problem seems to be
solved now. My case was basically having JAVA_OPTS that look like this before calling the
jboss-cli with bash:
{code:java}
$ export JAVA_OPTS="-Dtestparameter=\"Something with spaces\""
$ ./jboss-cli.sh
Error: Could not find or load main class with
Caused by: java.lang.ClassNotFoundException: with
{code}
This was tested on various unix operating systems and was specific to jboss-cli.sh, the
Windows variant was fine. We tested WF10 (no error), WF21 (error above), WF22 (no error).
No combination of escaping and quotes has worked on WF21. The temporary workaround we use
while using WF21 is temporarily unsetting JAVA_OPTS before using the jboss-cli which works
well.
EAP Pod fails to start when env
JBOSS_MODULEPATH=${JBOSS_HOME}/modules:${HOME} is set
-------------------------------------------------------------------------------------
Key: WFCORE-5216
URL: https://issues.redhat.com/browse/WFCORE-5216
Project: WildFly Core
Issue Type: Bug
Components: Scripts
Reporter: Ivo Studensky
Assignee: Ivo Studensky
Priority: Major
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:
{noformat}
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)
{noformat}
This issue does not occur on JBoss EAP 7.2 container.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)