Loading...

XML

Word

Printable

Type: Feature Request
Resolution: Done
Priority: Major
Fix Version/s: 13.0.0.Beta1, 13.0.0.Final
Affects Version/s: None
Component/s: Launcher, Scripts
Labels:
None

Git Pull Request:
https://github.com/wildfly/wildfly-core/pull/4131

Currently the scripts have an environment variable MODULE_OPTS which is used to enable the security manager for JBoss Modules. This variable is not currently allowed to be set yet in the *.conf files however we could expose it. The need for this comes from ~~WFCORE-4674~~ where the fix will be to add JBoss Modules as an agent, then add -javaagent:some-agent.jar to the arguments for JBoss Modules.

blocks

CLOUD-3537 Update startup module / agent loading to not require bootclasspath/a

incorporates

WFCORE-5053 Prometheus JMX exporter jar, stops starting the wildfly server.

Closed

is blocked by

WFCORE-4899 Upgrade jboss-modules from 1.10.0.Final to 1.10.1.Final

Closed

is related to

WFCORE-4674 Custom handlers, formatters and filters cause the server to crash if the log manager is on the boot class path

Closed

MODULES-393 Make jboss-modules a Java agent and allow other agents to be set as module arguments

Resolved

relates to

WFARQ-138 Add support in managed containers for passing MODULE_OPTS

Resolved

WFCORE-4504 Java Agent using JUL causes JBoss LogManager issues

Closed

WFMP-210 Add support in managed containers for passing MODULE_OPTS

Closed

BYTEMAN-398 Check the entry points class loader before using the system class loader

Closed

(4 relates to)

Assignee:: James Perkins

Reporter:: James Perkins

Votes:: 0 Vote for this issue

Watchers:: 2 Start watching this issue

Created:: 2019/11/13 3:44 PM

Updated:: 2023/12/24 10:39 PM

Resolved:: 2020/06/22 4:46 AM

Details

Description

Attachments

Issue Links

Activity

People

Dates