You should also be able to change the log4j.properties file so that its
doing ${catalina.home}/logs/cas.log.

I've considered setting that as the default but that assumes everyone uses
Tomcat.

Cheers,
Scott


On Thu, Nov 19, 2009 at 1:36 PM, Marvin Addison <[email protected]>wrote:

> My hunch is it's failing on trying to create the cas.log file since
> the failure is emanating from commons-logging LogFactory class:
>
> > Caused by: java.security.AccessControlException: access denied
> > (java.util.PropertyPermission
> > org.apache.commons.logging.LogFactory.HashtableImpl read)
> > at
> >
> java.security.AccessControlContext.checkPermission(AccessControlContext.java:342)
> > at
> java.security.AccessController.checkPermission(AccessController.java:553)
> > at java.lang.SecurityManager.checkPermission(SecurityManager.java:549)
> > at
> java.lang.SecurityManager.checkPropertyAccess(SecurityManager.java:1302)
> > at java.lang.System.getProperty(System.java:669)
>
> That would explain the absence of your cas.log file.  Please ensure
> that the user running tomcat has privileges to write to the current
> working directory.  Alternatively, customize
>
> $TOMCAT_HOME/webapps/cas-server-webapp-3.3.3/WEB-INF/classes/log4j.properties
> to write the log file to a well-known location, e.g. /var/log/cas.log,
> where you have write privileges.
>
> M
>
> --
> You are currently subscribed to [email protected] as:
> [email protected]
> To unsubscribe, change settings or access archives, see
> http://www.ja-sig.org/wiki/display/JSG/cas-user
>

-- 
You are currently subscribed to [email protected] as: 
[email protected]
To unsubscribe, change settings or access archives, see 
http://www.ja-sig.org/wiki/display/JSG/cas-user

Reply via email to