[
https://issues.jboss.org/browse/WFLY-10242?page=com.atlassian.jira.plugin...
]
David Lloyd commented on WFLY-10242:
------------------------------------
There is no circumstance, past or present, where {{-secmgr}} was allowed, added, or
supported in {{JAVA_OPTS}}.
The old way to run with a security manager, before (I believe) WF 10, was to pass the
system property {{java.security.manager}} in to the JVM's arguments. After WF 10, the
way to do it was to pass {{-secmgr}} into the startup script, which in turn put
{{-segmgr}} into the argument list of JBoss Modules (_not_ the JVM itself) causing our own
security manager to be enabled.
Unify secmgr JAVA_OPTS behaviour in WF scripts
----------------------------------------------
Key: WFLY-10242
URL:
https://issues.jboss.org/browse/WFLY-10242
Project: WildFly
Issue Type: Bug
Components: Scripts
Reporter: Marek Kopecký
Assignee: Kabir Khan
Unify secmgr JAVA_OPTS behaviour in WF scripts.
standalone&&domain&&appclient scripts doesn't allow to use secmgr by
JAVA_OPTS definition. wsconsume&&wsprovide scripts allow that (see
[
this|https://github.com/wildfly/wildfly/blob/master/feature-pack/src/main...]
and
[
this|https://github.com/wildfly/wildfly/blob/master/feature-pack/src/main...])
All scripts should be unified.
cc: [~asoldano], [~jamezp], [~jbliznak], [~msvehla]
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)