You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@archiva.apache.org by "Maria Odea Ching (JIRA)" <ji...@codehaus.org> on 2008/08/14 05:58:27 UTC
[jira] Created: (MRM-910) appserver.base property not resolved in
log4j.xml when deployed in Tomcat
appserver.base property not resolved in log4j.xml when deployed in Tomcat
-------------------------------------------------------------------------
Key: MRM-910
URL: http://jira.codehaus.org/browse/MRM-910
Project: Archiva
Issue Type: Bug
Components: web application
Affects Versions: 1.1.1, 1.1.2
Environment: Tomcat 6
Ubuntu Linux
archiva-1.2-SNAPSHOT (-r685734)
Reporter: Maria Odea Ching
Fix For: 1.1.x
Even after setting export CATALINA_OPTS="-Dappserver.home=$CATALINA_HOME -Dappserver.base=$CATALINA_HOME" before starting Tomcat, the appserver.base property seems to not have been resolved.
Here's a short snippet from the console during startup:
INFO: Starting Servlet Engine: Apache Tomcat/6.0.14
Aug 14, 2008 11:49:31 AM org.springframework.web.context.ContextLoader initWebApplicationContext
INFO: Root WebApplicationContext: initialization started
log4j:ERROR setFile(null,true) call failed.
java.io.FileNotFoundException: /logs/archiva.log (No such file or directory)
at java.io.FileOutputStream.openAppend(Native Method)
at java.io.FileOutputStream.<init>(FileOutputStream.java:177)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MRM-910) appserver.base property not resolved in
log4j.xml when deployed in Tomcat
Posted by "Maria Odea Ching (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maria Odea Ching updated MRM-910:
---------------------------------
Fix Version/s: 1.1.x
> appserver.base property not resolved in log4j.xml when deployed in Tomcat
> -------------------------------------------------------------------------
>
> Key: MRM-910
> URL: http://jira.codehaus.org/browse/MRM-910
> Project: Archiva
> Issue Type: Bug
> Components: web application
> Affects Versions: 1.1.1, 1.1.2
> Environment: Tomcat 6
> Ubuntu Linux
> archiva-1.2-SNAPSHOT (-r685734)
> Reporter: Maria Odea Ching
> Fix For: 1.1.x
>
>
> Even after setting export CATALINA_OPTS="-Dappserver.home=$CATALINA_HOME -Dappserver.base=$CATALINA_HOME" before starting Tomcat, the appserver.base property seems to not have been resolved.
> Here's a short snippet from the console during startup:
> INFO: Starting Servlet Engine: Apache Tomcat/6.0.14
> Aug 14, 2008 11:49:31 AM org.springframework.web.context.ContextLoader initWebApplicationContext
> INFO: Root WebApplicationContext: initialization started
> log4j:ERROR setFile(null,true) call failed.
> java.io.FileNotFoundException: /logs/archiva.log (No such file or directory)
> at java.io.FileOutputStream.openAppend(Native Method)
> at java.io.FileOutputStream.<init>(FileOutputStream.java:177)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira