That sorted it, Thank you, it is a real bind trying to work out what files are needed and what files are not needed.
and I only touched EJb;s and Tomcat/openejb for the first time 3 weeks ago, this group has been a great help and I am just greatful that there is so much help available for us beginners. Mike. > -----Original Message----- > From: Yansheng Lin [mailto:[EMAIL PROTECTED] > Sent: 10 March 2004 20:20 > To: 'Tomcat Users List' > Subject: RE: Log4j initialisation problem. > > > Hi, the Logger component you are looking at has nothing to do > with log4j. Also > you are using a relative path for the prefix. Try to use > "${TOMCAT_HOME}/logs/mysite_tomcat_log." or simply the absolute path. > > For log4j, I think the following instruction will get you going on your > log4j:WARN problem. > ------------------------------------------------------------ > To have Tomcat use log4j universally, place both log4j.jar and the Jakarta > commons-logging.jar into the $TOMCAT_HOME/common/lib directory. > Create your > log4j properties file as $TOMCAT_HOME/common/classes/log4j.properties and > configure the root logger. Here is the basic log4j.properties I > used for this > myself: > > log4j.rootLogger=info, R > log4j.appender.R=org.apache.log4j.ConsoleAppender > log4j.appender.R.layout=org.apache.log4j.PatternLayout > log4j.appender.R.layout.ConversionPattern=%-5p %-30.30c{1} %x - %m%n > > If you only need to use log4j in your own web app, just include > log4j (and any > log4j properties file) in your WAR. > ------------------------------------------------------------- > > > > -----Original Message----- > From: Michael Forster [mailto:[EMAIL PROTECTED] > Sent: Wednesday, March 10, 2004 12:47 PM > To: Tomcat Users List > Subject: RE: Log4j initialisation problem. > > > the files and entries are as follows - the error on writing the .xml file > (causing a reload) was also as follows > > log4j:WARN No appenders could be found for logger > (org.apache.catalina.session.ManagerBase). > log4j:WARN Please initialize the log4j system properly. > > In the mysite.xml file > <Logger className="org.apache.catalina.logger.FileLogger" > prefix="/dev/tomcat/logs/mysite_tomcat_log." suffix=".txt" > timestamp="true"/> > > > Mike. > > -----Original Message----- > > From: Yansheng Lin [mailto:[EMAIL PROTECTED] > > Sent: 10 March 2004 19:39 > > To: 'Tomcat Users List' > > Subject: RE: Log4j initialisation problem. > > > > > > Sounds to me like a path problem. you moved the context two > > levels down when > > you upgraded from 4 to 5. no? > > > > -----Original Message----- > > From: Michael Forster [mailto:[EMAIL PROTECTED] > > Sent: Wednesday, March 10, 2004 12:18 PM > > To: Tomcat-User > > Subject: Log4j initialisation problem. > > > > > > I recently had to upgrade from 4.1 to 5 > > The new server is running and I have extracted the context out of the > > server.xml and into the Catalina/localhost/file.xml > > > > but I am getting the following problem > > > > INFO: Processing Context configuration file URL > > file:C:\dev\tomcat\conf\Catalina\localhost\mysite.xml > > log4j:WARN No appenders could be found for logger > > (org.apache.catalina.startup.TldConfig). > > log4j:WARN Please initialize the log4j system properly. > > > > What am I missing? I cannot find any info on the web that describes this > > problem > > the logging.conf is in the right place why is it not using it > (or if it is > > what has changed from 4.1 to 5 > > > > Mike. > > > > -----BEGIN GEEK CODE BLOCK----- > > Version: 3.12 > > GCM d- s:+ a C++++ UL++++ P+ L+++ E--- W+++ N+++ o+ K w++++ > > O-- M- V- PS+ PE+ Y+ PGP t+++ 5+++ X- R+++ tv++ h++ DI++++ D++ > > G e+ h++ r+++ y+++ > > ------END GEEK CODE BLOCK------ > > --- > > Outgoing mail is certified Virus Free. > > Checked by AVG anti-virus system (http://www.grisoft.com). > > Version: 6.0.615 / Virus Database: 394 - Release Date: 08/03/2004 > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > --- > > Incoming mail is certified Virus Free. > > Checked by AVG anti-virus system (http://www.grisoft.com). > > Version: 6.0.615 / Virus Database: 394 - Release Date: 08/03/2004 > > > --- > Outgoing mail is certified Virus Free. > Checked by AVG anti-virus system (http://www.grisoft.com). > Version: 6.0.615 / Virus Database: 394 - Release Date: 08/03/2004 > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --- > Incoming mail is certified Virus Free. > Checked by AVG anti-virus system (http://www.grisoft.com). > Version: 6.0.615 / Virus Database: 394 - Release Date: 08/03/2004 > --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.615 / Virus Database: 394 - Release Date: 08/03/2004 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
