[jboss-jira] [JBoss JIRA] Created: (JBAS-4918) for logging, server.xml references another variable than jboss-log4j.xml does

Jon Stevens (JIRA) jira-events at lists.jboss.org
Mon Oct 29 19:53:01 EDT 2007


for logging, server.xml references another variable than jboss-log4j.xml does
-----------------------------------------------------------------------------

                 Key: JBAS-4918
                 URL: http://jira.jboss.com/jira/browse/JBAS-4918
             Project: JBoss Application Server
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Logging
    Affects Versions: JBossAS-4.2.0.GA
         Environment: all
            Reporter: Jon Stevens
         Assigned To: Scott M Stark


jboss-log4j.xml has this as default:

      <param name="File" value="${jboss.server.log.dir}/server.log"/>

jboss-web.deployer has this:

            <!-- Access logger -->
            <Valve className="org.apache.catalina.valves.AccessLogValve"
                prefix="localhost_access_log." suffix=".log"
                pattern="common" directory="${jboss.server.home.dir}/log" 
                resolveHosts="false" />

Now, because those two variables are different, I can't easily setup logging to say /var/log/jboss because

#1. there is two different variables to define: ${jboss.server.home.dir} and ${jboss.server.log.dir}
#2. the access logger has /log hard coded to the end of the directory attribute which makes it impossible to set the two variables to the same value.

My preference would be that the default is made to a single variable ${jboss.server.log.dir} which can control everything.

jon

-- 
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

        



More information about the jboss-jira mailing list