[
https://issues.jboss.org/browse/WFLY-9538?page=com.atlassian.jira.plugin....
]
R Searls commented on WFLY-9538:
--------------------------------
The documentation for -segmgr states that setting env var SECMGR=true will set this flag.
scripts standalone.sh, appclient.sh, domain.sh, common.ps1, and appclient.sh
all check for old value and present msg,
{code:java}
-Djava.security.manager)
echo "ERROR: The use of -Djava.security.manager has been removed. Please
use the -secmgr command line argument or SECMGR=true environment variable."
{code}
This utility should probably have the same check and report the same message. In
addition it should check for and use env var SECMGR.
wsprovide.sh does not support the -secmgr setting properly
----------------------------------------------------------
Key: WFLY-9538
URL:
https://issues.jboss.org/browse/WFLY-9538
Project: WildFly
Issue Type: Bug
Components: Scripts
Affects Versions: 10.0.0.Final
Reporter: R Searls
Assignee: Tomaz Cerar
wsprovide.sh, wsprovide.bat does not generate the cmd with the -secmgr flag in the
proper position. Changes to jboss-module.jar requires -segmgr to reside just after
the jboss-module.jar reference like this.
{code:java}
eval \"$JAVA\" $JAVA_OPTS \
-jar \""$JBOSS_HOME"/jboss-modules.jar\" \
*-secmgr \ *
-mp \""$JBOSS_HOME"/modules\" \
org.jboss.ws.tools.wsprovide \
'"$@"'
{code}
Current the old style and this new style value is passed in via the JAVA_OPTS env var.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)