[jboss-jira] [JBoss JIRA] (AS7-4271) Boot log writer ignores -Djboss.server.base.dir

[Heiko Rupp (JIRA)]

     [ https://issues.jboss.org/browse/AS7-4271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Heiko Rupp updated AS7-4271:
----------------------------

    Description: 
When on OS/X you start a server with -Djboss.server.base.dir  this directory is used for configuration and also server.log, but not to populate the boot.log, which is still written to standalone/logs/boot.log.

This is bad, as it will overwrite a boot.log for a server configuration that is running in parallel without -Djboss.server.base.dir= flag.
Actually the logging config also seems to point at the old place


hrupp          78046   0,0  1,1  1537296  96228 s005  S+   10:55am   0:03.70 /usr/bin/java -D[Standalone] -d32 -client -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Djboss.server.default.config=standalone.xml -Dorg.jboss.boot.log.file=/devel/jboss-as-7.1.1.Final/standalone/log/boot.log -Dlogging.configuration=file:/devel/jboss-as-7.1.1.Final/standalone/configuration/logging.properties -jar /devel/jboss-as-7.1.1.Final/jboss-modules.jar -mp /devel/jboss-as-7.1.1.Final/modules -jaxpmodule javax.xml.jaxp-provider org.jboss.as.standalone -Djboss.home.dir=/devel/jboss-as-7.1.1.Final -Djboss.server.base.dir=/devel/jboss-as-7.1.1.Final/standalone2



Turns out that the magic to detect -Djboss.server.base.dir in standalone.sh only works for linux:

if $linux; then
    # consolidate the server and command line opts
    SERVER_OPTS="$JAVA_OPTS $@"
    # process the standalone options
    for var in $SERVER_OPTS


as readlink is using '-m' flag that does not exist on OS/X

  was:
When you start a server with -Djboss.server.base.dir  this directory is used for configuration and also server.log, but not to populate the boot.log, which is still written to standalone/logs/boot.log.

This is bad, as it will overwrite a boot.log for a server configuration that is running in parallel without -Djboss.server.base.dir= flag.
Actually the logging config also seems to point at the old place


hrupp          78046   0,0  1,1  1537296  96228 s005  S+   10:55am   0:03.70 /usr/bin/java -D[Standalone] -d32 -client -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Djboss.server.default.config=standalone.xml -Dorg.jboss.boot.log.file=/devel/jboss-as-7.1.1.Final/standalone/log/boot.log -Dlogging.configuration=file:/devel/jboss-as-7.1.1.Final/standalone/configuration/logging.properties -jar /devel/jboss-as-7.1.1.Final/jboss-modules.jar -mp /devel/jboss-as-7.1.1.Final/modules -jaxpmodule javax.xml.jaxp-provider org.jboss.as.standalone -Djboss.home.dir=/devel/jboss-as-7.1.1.Final -Djboss.server.base.dir=/devel/jboss-as-7.1.1.Final/standalone2


    
> Boot log writer ignores -Djboss.server.base.dir
> -----------------------------------------------
>
>                 Key: AS7-4271
>                 URL: https://issues.jboss.org/browse/AS7-4271
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: Domain Management
>    Affects Versions: 7.1.1.Final
>            Reporter: Heiko Rupp
>            Assignee: Brian Stansberry
>              Labels: rhq
>
> When on OS/X you start a server with -Djboss.server.base.dir  this directory is used for configuration and also server.log, but not to populate the boot.log, which is still written to standalone/logs/boot.log.
> This is bad, as it will overwrite a boot.log for a server configuration that is running in parallel without -Djboss.server.base.dir= flag.
> Actually the logging config also seems to point at the old place
> hrupp          78046   0,0  1,1  1537296  96228 s005  S+   10:55am   0:03.70 /usr/bin/java -D[Standalone] -d32 -client -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Djboss.server.default.config=standalone.xml -Dorg.jboss.boot.log.file=/devel/jboss-as-7.1.1.Final/standalone/log/boot.log -Dlogging.configuration=file:/devel/jboss-as-7.1.1.Final/standalone/configuration/logging.properties -jar /devel/jboss-as-7.1.1.Final/jboss-modules.jar -mp /devel/jboss-as-7.1.1.Final/modules -jaxpmodule javax.xml.jaxp-provider org.jboss.as.standalone -Djboss.home.dir=/devel/jboss-as-7.1.1.Final -Djboss.server.base.dir=/devel/jboss-as-7.1.1.Final/standalone2
> Turns out that the magic to detect -Djboss.server.base.dir in standalone.sh only works for linux:
> if $linux; then
>     # consolidate the server and command line opts
>     SERVER_OPTS="$JAVA_OPTS $@"
>     # process the standalone options
>     for var in $SERVER_OPTS
> as readlink is using '-m' flag that does not exist on OS/X

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira