[JBoss JIRA] Created: (JBAS-5240) boot.log should print command line options ($JAVA_OPTS) by default
5:48 p.m.
boot.log should print command line options ($JAVA_OPTS) by default
------------------------------------------------------------------
Key: JBAS-5240
URL: http://jira.jboss.com/jira/browse/JBAS-5240
Project: JBoss Application Server
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Other
Affects Versions: JBossAS-5.0.0.Beta4, JBossAS-4.2.2.GA
Reporter: Galder Zamarreno
Assigned To: Galder Zamarreno
Priority: Minor
To help remote support, AS should by default log command line options
within boot.log as explained in " Logging command line options in boot.log"
section in http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossBootLogging
Thoughts?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:42 a.m.
New subject: [JBoss JIRA] Updated: (JBAS-5240) boot.log should print command line options ($JAVA_OPTS) by default
[ http://jira.jboss.com/jira/browse/JBAS-5240?page=all ]
Luc Texier updated JBAS-5240:
-----------------------------
Priority: Critical (was: Minor)
boot.log should print command line options ($JAVA_OPTS) by default
------------------------------------------------------------------
Key: JBAS-5240
URL: http://jira.jboss.com/jira/browse/JBAS-5240
Project: JBoss Application Server
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Other
Affects Versions: JBossAS-5.0.0.Beta4, JBossAS-4.2.2.GA
Reporter: Galder Zamarreno
Assigned To: Galder Zamarreno
Priority: Critical
To help remote support, AS should by default log command line options
within boot.log as explained in " Logging command line options in boot.log"
section in http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossBootLogging
Thoughts?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:44 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-5240) boot.log should print command line options ($JAVA_OPTS) by default
[ http://jira.jboss.com/jira/browse/JBAS-5240?page=comments#action_12400691 ]
Luc Texier commented on JBAS-5240:
----------------------------------
Absolutely. We need this enhancement asap to help Support understand faster customer's
installations
I am increasing the priority to Critical
boot.log should print command line options ($JAVA_OPTS) by default
------------------------------------------------------------------
Key: JBAS-5240
URL: http://jira.jboss.com/jira/browse/JBAS-5240
Project: JBoss Application Server
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Other
Affects Versions: JBossAS-5.0.0.Beta4, JBossAS-4.2.2.GA
Reporter: Galder Zamarreno
Assigned To: Galder Zamarreno
Priority: Critical
Fix For: JBossAS-4.2.3.GA, JBossAS-5.0.0.CR1
To help remote support, AS should by default log command line options
within boot.log as explained in " Logging command line options in boot.log"
section in http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossBootLogging
Thoughts?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:44 a.m.
New subject: [JBoss JIRA] Updated: (JBAS-5240) boot.log should print command line options ($JAVA_OPTS) by default
[ http://jira.jboss.com/jira/browse/JBAS-5240?page=all ]
Luc Texier updated JBAS-5240:
-----------------------------
Fix Version/s: JBossAS-5.0.0.CR1
JBossAS-4.2.3.GA
boot.log should print command line options ($JAVA_OPTS) by default
------------------------------------------------------------------
Key: JBAS-5240
URL: http://jira.jboss.com/jira/browse/JBAS-5240
Project: JBoss Application Server
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Other
Affects Versions: JBossAS-5.0.0.Beta4, JBossAS-4.2.2.GA
Reporter: Galder Zamarreno
Assigned To: Galder Zamarreno
Priority: Critical
Fix For: JBossAS-4.2.3.GA, JBossAS-5.0.0.CR1
To help remote support, AS should by default log command line options
within boot.log as explained in " Logging command line options in boot.log"
section in http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossBootLogging
Thoughts?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:42 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-5240) boot.log should print command line options ($JAVA_OPTS) by default
[ http://jira.jboss.com/jira/browse/JBAS-5240?page=comments#action_12401515 ]
Dimitris Andreadis commented on JBAS-5240:
------------------------------------------
It's not exactly trivial because at the time the options are parsed, there is no
configured logger.
boot.log should print command line options ($JAVA_OPTS) by default
------------------------------------------------------------------
Key: JBAS-5240
URL: http://jira.jboss.com/jira/browse/JBAS-5240
Project: JBoss Application Server
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Other
Affects Versions: JBossAS-5.0.0.Beta4, JBossAS-4.2.2.GA
Reporter: Galder Zamarreno
Assigned To: Galder Zamarreno
Priority: Critical
Fix For: JBossAS-5.0.0.CR1, JBossAS-4.2.3.GA
To help remote support, AS should by default log command line options
within boot.log as explained in " Logging command line options in boot.log"
section in http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossBootLogging
Thoughts?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:13 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-5240) boot.log should print command line options ($JAVA_OPTS) by default
[ http://jira.jboss.com/jira/browse/JBAS-5240?page=comments#action_12401725 ]
Galder Zamarreno commented on JBAS-5240:
----------------------------------------
I'm not sure I understand what you mean Dimitris. If you see the
wiki I pointed out in the description, you'll I've added the following:
"By default, command line parameters passed to JBoss Application
Server on startup are only logged in the console output. Within the
scope of remote support, this leads to users/customers being asked
to provide these options explicitly, as console output is often lost.
This can be avoided by adding the following line to java execution in
run.sh/bat:
-Djboss.java.opts="$JAVA_OPTS" \
to make the script look something like this:
...
if [ "x$LAUNCH_JBOSS_IN_BACKGROUND" = "x" ]; then
# Execute the JVM in the foreground
"$JAVA" $JAVA_OPTS \
-Djava.endorsed.dirs="$JBOSS_ENDORSED_DIRS" \
-Djboss.java.opts="$JAVA_OPTS" \
-classpath "$JBOSS_CLASSPATH" \
org.jboss.Main "$@"
JBOSS_STATUS=$?
else
# Execute the JVM in the background
"$JAVA" $JAVA_OPTS \
-Djava.endorsed.dirs="$JBOSS_ENDORSED_DIRS" \
-Djboss.java.opts="$JAVA_OPTS" \
-classpath "$JBOSS_CLASSPATH" \
org.jboss.Main "$@" &
JBOSS_PID=$!
...
On startup, ServerInfo class prints all system properties set on startup
to boot.log and so, by adding this new system property, we're effectively
forcing boot.log to print command line parameters passed on startup:
00:18:50,045 DEBUG [ServerInfo] jboss.java.opts: -Dprogram.name=run.sh -server
-Xms128m -Xmx512m
-Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Xdebug
-Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=y"
This solution worked fine for me. Am I missing something?
boot.log should print command line options ($JAVA_OPTS) by default
------------------------------------------------------------------
Key: JBAS-5240
URL: http://jira.jboss.com/jira/browse/JBAS-5240
Project: JBoss Application Server
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Other
Affects Versions: JBossAS-5.0.0.Beta4, JBossAS-4.2.2.GA
Reporter: Galder Zamarreno
Assigned To: Galder Zamarreno
Priority: Critical
Fix For: JBossAS-5.0.0.CR1, JBossAS-4.2.3.GA
To help remote support, AS should by default log command line options
within boot.log as explained in " Logging command line options in boot.log"
section in http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossBootLogging
Thoughts?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:03 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-5240) boot.log should print command line options ($JAVA_OPTS) by default
[ http://jira.jboss.com/jira/browse/JBAS-5240?page=comments#action_12401733 ]
Dimitris Andreadis commented on JBAS-5240:
------------------------------------------
Ok, I see. I understood you wanted to log all the command line options, including those
passed by the user at the command line, but you only talk about $JAVA_OPTS.
boot.log should print command line options ($JAVA_OPTS) by default
------------------------------------------------------------------
Key: JBAS-5240
URL: http://jira.jboss.com/jira/browse/JBAS-5240
Project: JBoss Application Server
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Other
Affects Versions: JBossAS-5.0.0.Beta4, JBossAS-4.2.2.GA
Reporter: Galder Zamarreno
Assigned To: Galder Zamarreno
Priority: Critical
Fix For: JBossAS-5.0.0.CR1, JBossAS-4.2.3.GA
To help remote support, AS should by default log command line options
within boot.log as explained in " Logging command line options in boot.log"
section in http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossBootLogging
Thoughts?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:18 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-5240) boot.log should print command line options ($JAVA_OPTS) by default
[ http://jira.jboss.com/jira/browse/JBAS-5240?page=comments#action_12401738 ]
Galder Zamarreno commented on JBAS-5240:
----------------------------------------
We, in support, are mostly interested in the VM parameters rather than
the JBoss AS parameters. It's parameters like Xmx, Xms, garbage collection
parameters, java net stack...etc that we're interested in getting logged.
I'm not too bothered about AS run parameters for the time being. Things like
-b are easy to discover because it sets two system properties (jboss.bind.address
and bind.address). -c can be guessed from the directory names.
boot.log should print command line options ($JAVA_OPTS) by default
------------------------------------------------------------------
Key: JBAS-5240
URL: http://jira.jboss.com/jira/browse/JBAS-5240
Project: JBoss Application Server
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Other
Affects Versions: JBossAS-5.0.0.Beta4, JBossAS-4.2.2.GA
Reporter: Galder Zamarreno
Assigned To: Galder Zamarreno
Priority: Critical
Fix For: JBossAS-5.0.0.CR1, JBossAS-4.2.3.GA
To help remote support, AS should by default log command line options
within boot.log as explained in " Logging command line options in boot.log"
section in http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossBootLogging
Thoughts?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:49 a.m.
New subject: [JBoss JIRA] Updated: (JBAS-5240) log $JAVA_OPTS in boot.log, by setting the 'jboss.java.opts' environment variable at start-up
[ http://jira.jboss.com/jira/browse/JBAS-5240?page=all ]
Dimitris Andreadis updated JBAS-5240:
-------------------------------------
Summary: log $JAVA_OPTS in boot.log, by setting the 'jboss.java.opts'
environment variable at start-up (was: boot.log should print command line options
($JAVA_OPTS) by default)
log $JAVA_OPTS in boot.log, by setting the 'jboss.java.opts'
environment variable at start-up
---------------------------------------------------------------------------------------------
Key: JBAS-5240
URL: http://jira.jboss.com/jira/browse/JBAS-5240
Project: JBoss Application Server
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Other
Affects Versions: JBossAS-5.0.0.Beta4, JBossAS-4.2.2.GA
Reporter: Galder Zamarreno
Assigned To: Galder Zamarreno
Priority: Critical
Fix For: JBossAS-5.0.0.CR1, JBossAS-4.2.3.GA
To help remote support, AS should by default log command line options
within boot.log as explained in " Logging command line options in boot.log"
section in http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossBootLogging
Thoughts?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:53 a.m.
New subject: [JBoss JIRA] Resolved: (JBAS-5240) log $JAVA_OPTS in boot.log, by setting the 'jboss.java.opts' environment variable at start-up
[ http://jira.jboss.com/jira/browse/JBAS-5240?page=all ]
Dimitris Andreadis resolved JBAS-5240.
--------------------------------------
Resolution: Done
I've commited the changes in both run.sh and run.bat. Can you check it works for you
and also update the wiki?
log $JAVA_OPTS in boot.log, by setting the 'jboss.java.opts'
environment variable at start-up
---------------------------------------------------------------------------------------------
Key: JBAS-5240
URL: http://jira.jboss.com/jira/browse/JBAS-5240
Project: JBoss Application Server
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Other
Affects Versions: JBossAS-5.0.0.Beta4, JBossAS-4.2.2.GA
Reporter: Galder Zamarreno
Assigned To: Galder Zamarreno
Priority: Critical
Fix For: JBossAS-5.0.0.CR1, JBossAS-4.2.3.GA
To help remote support, AS should by default log command line options
within boot.log as explained in " Logging command line options in boot.log"
section in http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossBootLogging
Thoughts?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:47 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-5240) log $JAVA_OPTS in boot.log, by setting the 'jboss.java.opts' environment variable at start-up
[ http://jira.jboss.com/jira/browse/JBAS-5240?page=comments#action_12402137 ]
Galder Zamarreno commented on JBAS-5240:
----------------------------------------
Checked trunk and it's working fine. I'll update the wiki.
log $JAVA_OPTS in boot.log, by setting the 'jboss.java.opts'
environment variable at start-up
---------------------------------------------------------------------------------------------
Key: JBAS-5240
URL: http://jira.jboss.com/jira/browse/JBAS-5240
Project: JBoss Application Server
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Other
Affects Versions: JBossAS-5.0.0.Beta4, JBossAS-4.2.2.GA
Reporter: Galder Zamarreno
Assigned To: Galder Zamarreno
Priority: Critical
Fix For: JBossAS-5.0.0.CR1, JBossAS-4.2.3.GA
To help remote support, AS should by default log command line options
within boot.log as explained in " Logging command line options in boot.log"
section in http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossBootLogging
Thoughts?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:54 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-5240) log $JAVA_OPTS in boot.log, by setting the 'jboss.java.opts' environment variable at start-up
[ http://jira.jboss.com/jira/browse/JBAS-5240?page=comments#action_12402140 ]
Galder Zamarreno commented on JBAS-5240:
----------------------------------------
Wiki updated.
log $JAVA_OPTS in boot.log, by setting the 'jboss.java.opts'
environment variable at start-up
---------------------------------------------------------------------------------------------
Key: JBAS-5240
URL: http://jira.jboss.com/jira/browse/JBAS-5240
Project: JBoss Application Server
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Other
Affects Versions: JBossAS-5.0.0.Beta4, JBossAS-4.2.2.GA
Reporter: Galder Zamarreno
Assigned To: Galder Zamarreno
Priority: Critical
Fix For: JBossAS-5.0.0.CR1, JBossAS-4.2.3.GA
To help remote support, AS should by default log command line options
within boot.log as explained in " Logging command line options in boot.log"
section in http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossBootLogging
Thoughts?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:45 a.m.
New subject: [JBoss JIRA] Closed: (JBAS-5240) log $JAVA_OPTS in boot.log, by setting the 'jboss.java.opts' environment variable at start-up
[ http://jira.jboss.com/jira/browse/JBAS-5240?page=all ]
Dimitris Andreadis closed JBAS-5240.
------------------------------------
log $JAVA_OPTS in boot.log, by setting the 'jboss.java.opts'
environment variable at start-up
---------------------------------------------------------------------------------------------
Key: JBAS-5240
URL: http://jira.jboss.com/jira/browse/JBAS-5240
Project: JBoss Application Server
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Other
Affects Versions: JBossAS-5.0.0.Beta4, JBossAS-4.2.2.GA
Reporter: Galder Zamarreno
Assigned To: Galder Zamarreno
Priority: Critical
Fix For: JBossAS-5.0.0.CR1, JBossAS-4.2.3.GA
To help remote support, AS should by default log command line options
within boot.log as explained in " Logging command line options in boot.log"
section in http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossBootLogging
Thoughts?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:12 p.m.
New subject: [JBoss JIRA] Reopened: (JBAS-5240) log $JAVA_OPTS in boot.log, by setting the 'jboss.java.opts' environment variable at start-up
[ http://jira.jboss.com/jira/browse/JBAS-5240?page=all ]
Mladen Turk reopened JBAS-5240:
-------------------------------
In general both posix and windows scripts are broken if
JAVA_OPTS contains quoted param.
export JAVA_OPTS=-Djboss.foo="some param"
./run.sh
Exception in thread "main" java.lang.NoClassDefFoundError:
value
Caused by: java.lang.ClassNotFoundException: value
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:276)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
This is caused by -Djboss.java.opts="$(JAVA_OPTS)"
so if JAVA_OPTS contains quoted string one has invalid
command line cause its evaluated to:
-Djboss.java.opts="-server -Djboss.foo="some value""
So you have value" as main class, and that sucks :)
The solution would be to escape the $JAVA_OPTS for usage
in -Djboss.java.opts.
log $JAVA_OPTS in boot.log, by setting the 'jboss.java.opts'
environment variable at start-up
---------------------------------------------------------------------------------------------
Key: JBAS-5240
URL: http://jira.jboss.com/jira/browse/JBAS-5240
Project: JBoss Application Server
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Other
Affects Versions: JBossAS-5.0.0.Beta4, JBossAS-4.2.2.GA
Reporter: Galder Zamarreno
Assigned To: Galder Zamarreno
Priority: Critical
Fix For: JBossAS-5.0.0.CR1, JBossAS-4.2.3.GA
To help remote support, AS should by default log command line options
within boot.log as explained in " Logging command line options in boot.log"
section in http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossBootLogging
Thoughts?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:43 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-5240) log $JAVA_OPTS in boot.log, by setting the 'jboss.java.opts' environment variable at start-up
[ http://jira.jboss.com/jira/browse/JBAS-5240?page=comments#action_12403625 ]
Anil Saldhana commented on JBAS-5240:
-------------------------------------
I am rolling back Mladen;s change. JBoss5 does not start on cygwin/windows. Please check
and make the right fixes.
log $JAVA_OPTS in boot.log, by setting the 'jboss.java.opts'
environment variable at start-up
---------------------------------------------------------------------------------------------
Key: JBAS-5240
URL: http://jira.jboss.com/jira/browse/JBAS-5240
Project: JBoss Application Server
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Other
Affects Versions: JBossAS-5.0.0.Beta4, JBossAS-4.2.2.GA
Reporter: Galder Zamarreno
Assigned To: Galder Zamarreno
Priority: Critical
Fix For: JBossAS-5.0.0.CR1, JBossAS-4.2.3.GA
To help remote support, AS should by default log command line options
within boot.log as explained in " Logging command line options in boot.log"
section in http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossBootLogging
Thoughts?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:01 p.m.
New subject: [JBoss JIRA] Updated: (JBAS-5240) log $JAVA_OPTS in boot.log, by setting the 'jboss.java.opts' environment variable at start-up
[ http://jira.jboss.com/jira/browse/JBAS-5240?page=all ]
Dimitris Andreadis updated JBAS-5240:
-------------------------------------
Fix Version/s: (was: JBossAS-4.2.3.GA)
Reverted the changes in Branch_4_2.
log $JAVA_OPTS in boot.log, by setting the 'jboss.java.opts'
environment variable at start-up
---------------------------------------------------------------------------------------------
Key: JBAS-5240
URL: http://jira.jboss.com/jira/browse/JBAS-5240
Project: JBoss Application Server
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Other
Affects Versions: JBossAS-5.0.0.Beta4, JBossAS-4.2.2.GA
Reporter: Galder Zamarreno
Assigned To: Galder Zamarreno
Priority: Critical
Fix For: JBossAS-5.0.0.CR1
To help remote support, AS should by default log command line options
within boot.log as explained in " Logging command line options in boot.log"
section in http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossBootLogging
Thoughts?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:52 a.m.
New subject: [JBoss JIRA] Closed: (JBAS-5240) log $JAVA_OPTS in boot.log, by setting the 'jboss.java.opts' environment variable at start-up
[ http://jira.jboss.com/jira/browse/JBAS-5240?page=all ]
Dimitris Andreadis closed JBAS-5240.
------------------------------------
Fix Version/s: (was: JBossAS-5.0.0.CR1)
Resolution: Won't Fix
Assignee: Dimitris Andreadis (was: Galder Zamarreno)
Galder, I've reverted the related changes. The problem is when doing the following:
.bat
-Djboss.java.opts="%JAVA_OPTS%"
.sh
-Djboss.java.opts="$JAVA_OPTS"
We have a problem when JAVA_OPTS includes quotes, e.g. JAVA_OPTS=-Dsome.property="xy
and z"
I don't know an easy way to escape this in the .bat/.sh scripts, so I'm closing
this JIRA as won't fix.
If you find a better solution that works on all platforms, please re-open.
log $JAVA_OPTS in boot.log, by setting the 'jboss.java.opts'
environment variable at start-up
---------------------------------------------------------------------------------------------
Key: JBAS-5240
URL: http://jira.jboss.com/jira/browse/JBAS-5240
Project: JBoss Application Server
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Other
Affects Versions: JBossAS-5.0.0.Beta4, JBossAS-4.2.2.GA
Reporter: Galder Zamarreno
Assigned To: Dimitris Andreadis
Priority: Critical
To help remote support, AS should by default log command line options
within boot.log as explained in " Logging command line options in boot.log"
section in http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossBootLogging
Thoughts?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:52 a.m.
New subject: [JBoss JIRA] Reopened: (JBAS-5240) log $JAVA_OPTS in boot.log, by setting the 'jboss.java.opts' environment variable at start-up
[
https://jira.jboss.org/jira/browse/JBAS-5240?page=com.atlassian.jira.plug...
]
Galder Zamarreno reopened JBAS-5240:
------------------------------------
Assignee: Galder Zamarreno (was: Dimitris Andreadis)
Still wanna look at this at some point, so reopening and
assigning to myself.
log $JAVA_OPTS in boot.log, by setting the 'jboss.java.opts'
environment variable at start-up
---------------------------------------------------------------------------------------------
Key: JBAS-5240
URL: https://jira.jboss.org/jira/browse/JBAS-5240
Project: JBoss Application Server
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Other
Affects Versions: JBossAS-4.2.2.GA, JBossAS-5.0.0.Beta4
Reporter: Galder Zamarreno
Assignee: Galder Zamarreno
Priority: Critical
To help remote support, AS should by default log command line options
within boot.log as explained in " Logging command line options in boot.log"
section in http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossBootLogging
Thoughts?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:33 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-5240) log $JAVA_OPTS in boot.log, by setting the 'jboss.java.opts' environment variable at start-up
[
https://jira.jboss.org/jira/browse/JBAS-5240?page=com.atlassian.jira.plug...
]
Galder Zamarreno commented on JBAS-5240:
----------------------------------------
Think I found a way to show these VM parameters in boot.log:
java.lang.management.RuntimeMXBean.getInputArguments();
Returns the input arguments passed to the Java virtual machine which does not include the
arguments to the main method. This method returns an empty list if there is no input
argument to the Java virtual machine.
Some Java virtual machine implementations may take input arguments from multiple different
sources: for examples, arguments passed from the application that launches the Java
virtual machine such as the 'java' command, environment variables, configuration
files, etc.
Typically, not all command-line options to the 'java' command are passed to the
Java virtual machine. Thus, the returned input arguments may not include all command-line
options.
MBeanServer access:
The mapped type of List is String[].
Returns:
a list of String objects; each element is an argument passed to the Java virtual
machine.
Throws:
SecurityException - if a security manager exists and the caller does not have
ManagementPermission("monitor").
This is what JConsole uses to show the VM parameters in sun.tools.jconsole.SummaryTab.
Sample:
VM Information
Java Virtual Machine:
Java HotSpot(TM) Server VM version 1.5.0_16-b02
Vendor:
Sun Microsystems Inc.
Uptime:
6 minutes
Name:
17358(a)localhost.localdomain
VM arguments:
-XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/tmp/java_heap -XX:+UseConcMarkSweepGC
-XX:+UseParNewGC -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=21001
-Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false
-Dfile.encoding=UTF-8
log $JAVA_OPTS in boot.log, by setting the 'jboss.java.opts'
environment variable at start-up
---------------------------------------------------------------------------------------------
Key: JBAS-5240
URL: https://jira.jboss.org/jira/browse/JBAS-5240
Project: JBoss Application Server
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Other
Affects Versions: JBossAS-4.2.2.GA, JBossAS-5.0.0.Beta4
Reporter: Galder Zamarreno
Assignee: Galder Zamarreno
Priority: Critical
Fix For: JBossAS-5.1.0.GA, JBossAS-6.0.0.Alpha1
To help remote support, AS should by default log command line options
within boot.log as explained in " Logging command line options in boot.log"
section in http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossBootLogging
Thoughts?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:33 a.m.
New subject: [JBoss JIRA] Updated: (JBAS-5240) log $JAVA_OPTS in boot.log, by setting the 'jboss.java.opts' environment variable at start-up
[
https://jira.jboss.org/jira/browse/JBAS-5240?page=com.atlassian.jira.plug...
]
Galder Zamarreno updated JBAS-5240:
-----------------------------------
Fix Version/s: JBossAS-5.1.0.GA
JBossAS-6.0.0.Alpha1
log $JAVA_OPTS in boot.log, by setting the 'jboss.java.opts'
environment variable at start-up
---------------------------------------------------------------------------------------------
Key: JBAS-5240
URL: https://jira.jboss.org/jira/browse/JBAS-5240
Project: JBoss Application Server
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Other
Affects Versions: JBossAS-4.2.2.GA, JBossAS-5.0.0.Beta4
Reporter: Galder Zamarreno
Assignee: Galder Zamarreno
Priority: Critical
Fix For: JBossAS-5.1.0.GA, JBossAS-6.0.0.Alpha1
To help remote support, AS should by default log command line options
within boot.log as explained in " Logging command line options in boot.log"
section in http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossBootLogging
Thoughts?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:42 a.m.
New subject: [JBoss JIRA] Updated: (JBAS-5240) Log VM arguments in boot.log
[
https://jira.jboss.org/jira/browse/JBAS-5240?page=com.atlassian.jira.plug...
]
Galder Zamarreno updated JBAS-5240:
-----------------------------------
Summary: Log VM arguments in boot.log (was: log $JAVA_OPTS in boot.log, by setting
the 'jboss.java.opts' environment variable at start-up)
To avoid asking customers to upload console output or ask them spell out the VM parameters
for us.
Log VM arguments in boot.log
----------------------------
Key: JBAS-5240
URL: https://jira.jboss.org/jira/browse/JBAS-5240
Project: JBoss Application Server
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Other
Affects Versions: JBossAS-4.2.2.GA, JBossAS-5.0.0.Beta4
Reporter: Galder Zamarreno
Assignee: Galder Zamarreno
Priority: Critical
Fix For: JBossAS-5.1.0.GA, JBossAS-6.0.0.Alpha1
To help remote support, AS should by default log command line options
within boot.log as explained in " Logging command line options in boot.log"
section in http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossBootLogging
Thoughts?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:48 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-5240) Log VM arguments in boot.log
[
https://jira.jboss.org/jira/browse/JBAS-5240?page=com.atlassian.jira.plug...
]
Galder Zamarreno commented on JBAS-5240:
----------------------------------------
Example:
13:44:43,226 INFO [ServerInfo] VM arguments: -Dprogram.name=run.sh -Xms128m -Xmx512m
-XX:MaxPermSize=256m -Dorg.jboss.resolver.warning=true
-Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000
-Djava.net.preferIPv4Stack=true
-Djava.endorsed.dirs=/home/galder/jboss/code/as/trunk/build/output/jboss-6.0.0.Alpha1/lib/endorsed
This IMO makes the following line in the run script obsolete:
echo " JAVA_OPTS: $JAVA_OPTS"
Keeping this information in the logs, specially in boot.log makes support much much
easier.
Log VM arguments in boot.log
----------------------------
Key: JBAS-5240
URL: https://jira.jboss.org/jira/browse/JBAS-5240
Project: JBoss Application Server
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Other
Affects Versions: JBossAS-4.2.2.GA, JBossAS-5.0.0.Beta4
Reporter: Galder Zamarreno
Assignee: Galder Zamarreno
Priority: Critical
Fix For: JBossAS-5.1.0.GA, JBossAS-6.0.0.Alpha1
To help remote support, AS should by default log command line options
within boot.log as explained in " Logging command line options in boot.log"
section in http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossBootLogging
Thoughts?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:19 a.m.
New subject: [JBoss JIRA] Updated: (JBAS-5240) Log VM arguments in boot.log
[
https://jira.jboss.org/jira/browse/JBAS-5240?page=com.atlassian.jira.plug...
]
Dimitris Andreadis updated JBAS-5240:
-------------------------------------
Fix Version/s: JBossAS-5.1.0.Beta1
(was: JBossAS-5.1.0.GA)
(was: JBossAS-6.0.0.Alpha1)
Log VM arguments in boot.log
----------------------------
Key: JBAS-5240
URL: https://jira.jboss.org/jira/browse/JBAS-5240
Project: JBoss Application Server
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Other
Affects Versions: JBossAS-4.2.2.GA, JBossAS-5.0.0.Beta4
Reporter: Galder Zamarreno
Assignee: Galder Zamarreno
Priority: Critical
Fix For: JBossAS-5.1.0.Beta1
To help remote support, AS should by default log command line options
within boot.log as explained in " Logging command line options in boot.log"
section in http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossBootLogging
Thoughts?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:25 a.m.
New subject: [JBoss JIRA] Updated: (JBAS-5240) Log VM arguments in boot.log
[
https://jira.jboss.org/jira/browse/JBAS-5240?page=com.atlassian.jira.plug...
]
Dimitris Andreadis updated JBAS-5240:
-------------------------------------
Fix Version/s: JBossAS-6.0.0.Alpha1
Log VM arguments in boot.log
----------------------------
Key: JBAS-5240
URL: https://jira.jboss.org/jira/browse/JBAS-5240
Project: JBoss Application Server
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Other
Affects Versions: JBossAS-4.2.2.GA, JBossAS-5.0.0.Beta4
Reporter: Galder Zamarreno
Assignee: Galder Zamarreno
Priority: Critical
Fix For: JBossAS-5.1.0.Beta1, JBossAS-6.0.0.Alpha1
To help remote support, AS should by default log command line options
within boot.log as explained in " Logging command line options in boot.log"
section in http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossBootLogging
Thoughts?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:36 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-5240) Log VM arguments in boot.log
[
https://jira.jboss.org/jira/browse/JBAS-5240?page=com.atlassian.jira.plug...
]
Galder Zamarreno commented on JBAS-5240:
----------------------------------------
Agreed to leave the echo as it is.
Log VM arguments in boot.log
----------------------------
Key: JBAS-5240
URL: https://jira.jboss.org/jira/browse/JBAS-5240
Project: JBoss Application Server
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Other
Affects Versions: JBossAS-4.2.2.GA, JBossAS-5.0.0.Beta4
Reporter: Galder Zamarreno
Assignee: Galder Zamarreno
Priority: Critical
Fix For: JBossAS-5.1.0.Beta1, JBossAS-6.0.0.Alpha1
To help remote support, AS should by default log command line options
within boot.log as explained in " Logging command line options in boot.log"
section in http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossBootLogging
Thoughts?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:48 a.m.
New subject: [JBoss JIRA] Resolved: (JBAS-5240) Log VM arguments in boot.log
[
https://jira.jboss.org/jira/browse/JBAS-5240?page=com.atlassian.jira.plug...
]
Galder Zamarreno resolved JBAS-5240.
------------------------------------
Resolution: Done
Log VM arguments in boot.log
----------------------------
Key: JBAS-5240
URL: https://jira.jboss.org/jira/browse/JBAS-5240
Project: JBoss Application Server
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Other
Affects Versions: JBossAS-4.2.2.GA, JBossAS-5.0.0.Beta4
Reporter: Galder Zamarreno
Assignee: Galder Zamarreno
Priority: Critical
Fix For: JBossAS-5.1.0.Beta1, JBossAS-6.0.0.Alpha1
To help remote support, AS should by default log command line options
within boot.log as explained in " Logging command line options in boot.log"
section in http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossBootLogging
Thoughts?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:53 p.m.
New subject: [JBoss JIRA] Closed: (JBAS-5240) Log VM arguments in boot.log
[
https://jira.jboss.org/jira/browse/JBAS-5240?page=com.atlassian.jira.plug...
]
Brian Stansberry closed JBAS-5240.
----------------------------------
Log VM arguments in boot.log
----------------------------
Key: JBAS-5240
URL: https://jira.jboss.org/jira/browse/JBAS-5240
Project: JBoss Application Server
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Other
Affects Versions: JBossAS-4.2.2.GA, JBossAS-5.0.0.Beta4
Reporter: Galder Zamarreno
Assignee: Galder Zamarreno
Priority: Critical
Fix For: JBossAS-5.1.0.Beta1
To help remote support, AS should by default log command line options
within boot.log as explained in " Logging command line options in boot.log"
section in http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossBootLogging
Thoughts?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:53 p.m.
New subject: [JBoss JIRA] Reopened: (JBAS-5240) Log VM arguments in boot.log
[
https://jira.jboss.org/jira/browse/JBAS-5240?page=com.atlassian.jira.plug...
]
Brian Stansberry reopened JBAS-5240:
------------------------------------
Log VM arguments in boot.log
----------------------------
Key: JBAS-5240
URL: https://jira.jboss.org/jira/browse/JBAS-5240
Project: JBoss Application Server
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Other
Affects Versions: JBossAS-4.2.2.GA, JBossAS-5.0.0.Beta4
Reporter: Galder Zamarreno
Assignee: Galder Zamarreno
Priority: Critical
Fix For: JBossAS-5.1.0.Beta1
To help remote support, AS should by default log command line options
within boot.log as explained in " Logging command line options in boot.log"
section in http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossBootLogging
Thoughts?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:53 p.m.
New subject: [JBoss JIRA] Resolved: (JBAS-5240) Log VM arguments in boot.log
[
https://jira.jboss.org/jira/browse/JBAS-5240?page=com.atlassian.jira.plug...
]
Brian Stansberry resolved JBAS-5240.
------------------------------------
Fix Version/s: (was: JBossAS-6.0.0.M3)
Resolution: Done
Removing extra Fix Version implied by earlier one.
Log VM arguments in boot.log
----------------------------
Key: JBAS-5240
URL: https://jira.jboss.org/jira/browse/JBAS-5240
Project: JBoss Application Server
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Other
Affects Versions: JBossAS-4.2.2.GA, JBossAS-5.0.0.Beta4
Reporter: Galder Zamarreno
Assignee: Galder Zamarreno
Priority: Critical
Fix For: JBossAS-5.1.0.Beta1
To help remote support, AS should by default log command line options
within boot.log as explained in " Logging command line options in boot.log"
section in http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossBootLogging
Thoughts?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5360
days inactive
6074
days old
28 comments
6 participants
participants (6)
-
Anil Saldhana (JIRA) -
Brian Stansberry (JIRA)
-
Dimitris Andreadis (JIRA)
-
Galder Zamarreno (JIRA)
-
Luc Texier (JIRA)
-
Mladen Turk (JIRA)