[
https://issues.jboss.org/browse/ARQ-1750?page=com.atlassian.jira.plugin.s...
]
Aslak Knutsen commented on ARQ-1750:
------------------------------------
[~gpoul] I would assume the jvm.options file was read by the Batch script that start the
java process. Since the managed container take over the role of the 'server'
script, we need to provide an alternative route to configure it. And yes, other containers
provide similar options as they need to be provided by the 'thing' starting the
JVM, and not by the JVM itself.
Support javaVmArguments configuration option to control forked vm
-----------------------------------------------------------------
Key: ARQ-1750
URL:
https://issues.jboss.org/browse/ARQ-1750
Project: Arquillian
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: WebSphere Containers
Affects Versions: was_1.0.0.Alpha2
Reporter: Aslak Knutsen
Support configuration option javaVmArguments to add extra information to the launched WLP
vm.
* memory settings
* debug options
java [javaVmArguments] -javaagent:lib/bootstrap-agent.jar -jar lib/ws-launch.jar
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira