Patrick McCarty created DAEMON-295:
--------------------------------------
Summary: Mysterious JVM argument: exit
Key: DAEMON-295
URL: https://issues.apache.org/jira/browse/DAEMON-295
Project: Commons Daemon
Issue Type: Bug
Components: Procrun
Affects Versions: 1.0.15
Environment: jvm mode using JDK7 server JVM on Windows
Reporter: Patrick McCarty
Priority: Trivial
I have a Windows service configured to use --StartMode=jvm. I noticed an
unexplained JVM argument 'exit' when my service prints out the active JVM
arguments at startup using the java code:
System.out.println("[Begin JVM arguments]");
for (final String jvmArg :
ManagementFactory.getRuntimeMXBean().getInputArguments())
{
System.out.println(jvmarg);
}
System.out.println("[End JVM arguments]");
For example:
[Begin JVM arguments]
-Xrs
-XX:+UseG1GC
exit
-Xms100m
-Xmx1024m
[End JVM arguments]
The arguments listed before 'exit' are those that I configured using
--JvmOptions=-Xrs;-XX:+UseG1GC. The arguments listed after 'exit' were added by
procrun itself based on the --JvmMs and --JvmMx arguments that I specified (if
not specified, exit will be the last argument). But where did exit come from?
Why is it added as a JVM argument?
Although I have not noticed any ill effects, this seems like a bug to me as I
don't believe exit was added intentionally. The same behavior is observed
whether run as a procrun service, or using the procrun console mode, but not
when running normally using java -server -Xrs -XX:+UseG1GC -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
