[jboss-jira] [JBoss JIRA] Commented: (JBAS-5240) Log VM arguments in boot.log

[Galder Zamarreno (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBAS-5240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12453070#action_12453070 ] 

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