Those solutions work, but coding ${catalina.home} or ${jboss.home.dir} in CAS's
log4.properties file would make it not work on the other server (and we use
both).
Both Tomcat and jBoss have a server-supplied log4j.properties, and all of our
other apps rely it for log4j configuration.
Would CAS have a problem if we remove the CAS-provided log4j.properties file
and rely on the one from Tomcat/jBoss? The answer depends on *how* CAS reads
its log4j properties.
From: Andrew R Feller [mailto:[email protected]]
Sent: Wednesday, July 15, 2009 7:28 PM
To: [email protected]
Subject: RE: [cas-user] cas.log location
CAS defers to Log4J on where to store the logs. By default, it will create it
in the directory where your servlet container is started. If you ran Apache
Tomcat, you could change the location to ${catalina.home}/logs/cas.log and it
would understand that. I don't know if JBoss creates a system property like
${catalina.home}, but something like that is what I would recommend. Tomcat is
at the heart of JBoss AS, so give it a whirl and see.
A-
--
Andrew Feller, Analyst
LSU University Information Services
200 Frey Computing Services Center
Baton Rouge, LA 70803
Office: 225.578.3737
Fax: 225.578.6400
-----Original Message-----
From: Bruno Melloni [mailto:[email protected]]
Sent: Wed 7/15/2009 4:21 PM
To: [email protected]
Subject: [cas-user] cas.log location
I am in a bit of a strange situation that m not quite sure how to solve.
- We run CAS 3.3.1 in our formal servers under Windows on jBoss. In
those servers we place jBoss on the D: drive and run it as a Windows service.
- In our developers workstations we usually run in Tomcat, and
sometimes on jBoss for thorough testing. In these boxes the servers are
started manually, and the whole thing is in the C: drive.
One of the things we noticed was that if we use the default CAS log4.properties
and launch it from a service, cas.log ends up in C:/Windows/System3 a horrible
place for i especially since it is our policy to put nothing but stock Windows
in the C: drive of our formal servers.
So, we modified C log4j.properties and set the location of the CAS log file to
d:/jBoss/logs/cas.log. That forces the log file to the D: drive (most
critical), and puts it in a better location. Bu that now causes an error in
the developers boxes since they have no D: drive.
Is there a good solution for this situation?
If we removed CA log4j.properties from the application, will CAS be smart
enough to automatically default to the servs log4j configuration instead of
expecting its own?
Thanks,
bruno
--
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
--
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
