Re: log4j :ERROR LogMananger.repositorySelector was null likely duetoerror

2010-03-02 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Chuck, On 2/26/2010 3:54 PM, Caldarale, Charles R wrote: >> From: Christopher Schultz [mailto:ch...@christopherschultz.net] >> Subject: Re: log4j :ERROR LogMananger.repositorySelector was null >> likely duetoerror >> &g

RE: log4j :ERROR LogMananger.repositorySelector was null likely duetoerror

2010-02-26 Thread Caldarale, Charles R
> From: Christopher Schultz [mailto:ch...@christopherschultz.net] > Subject: Re: log4j :ERROR LogMananger.repositorySelector was null > likely duetoerror > > 4) Use jinfo, a program that comes with the JDK for sure, possibly with > the JRE as well. It doesn't come wit

Re: log4j :ERROR LogMananger.repositorySelector was null likely dueto error

2010-02-26 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Chuck, On 2/26/2010 9:13 AM, Caldarale, Charles R wrote: >> From: Christoph Kukulies [mailto:k...@kukulies.org] >> Subject: Re: log4j :ERROR LogMananger.repositorySelector was null >> likely dueto error >> >> Is there a

RE: log4j :ERROR LogMananger.repositorySelector was null likely dueto error

2010-02-26 Thread Caldarale, Charles R
> From: Christoph Kukulies [mailto:k...@kukulies.org] > Subject: Re: log4j :ERROR LogMananger.repositorySelector was null > likely dueto error > > Is there a way to interrogate the running tomcat (catalina) process > about it's set parameters? 1) Use JConsole (tricky with

RE: log4j :ERROR LogMananger.repositorySelector was null likely due to error

2010-02-26 Thread Caldarale, Charles R
> From: Christoph Kukulies [mailto:k...@kukulies.org] > Subject: Re: log4j :ERROR LogMananger.repositorySelector was null > likely due to error > > Since passing start parameters under Windows (service manager) is weird Use the Java tab of the tomcat6w.exe program to set startup

Re: log4j :ERROR LogMananger.repositorySelector was null likely due to error

2010-02-26 Thread André Warnier
Christoph Kukulies wrote: Mark Thomas schrieb: On 26/02/2010 11:16, Christoph Kukulies wrote: Mark Thomas schrieb: On 26/02/2010 09:47, Christoph Kukulies wrote: I would be glad if I could get some help on m problem getting solved here. http://tomcat.apache.org/tomcat-6.0-doc/config/systemp

Re: log4j :ERROR LogMananger.repositorySelector was null likely due to error

2010-02-26 Thread Christoph Kukulies
Mark Thomas schrieb: On 26/02/2010 11:16, Christoph Kukulies wrote: Mark Thomas schrieb: On 26/02/2010 09:47, Christoph Kukulies wrote: I would be glad if I could get some help on m problem getting solved here. http://tomcat.apache.org/tomcat-6.0-doc/config/systemprops.html org.apache.catali

Re: log4j :ERROR LogMananger.repositorySelector was null likely due to error

2010-02-26 Thread Christoph Kukulies
Mark Thomas schrieb: On 26/02/2010 11:16, Christoph Kukulies wrote: Mark Thomas schrieb: On 26/02/2010 09:47, Christoph Kukulies wrote: I would be glad if I could get some help on m problem getting solved here. http://tomcat.apache.org/tomcat-6.0-doc/config/systemprops.html org.apache.catali

Re: log4j :ERROR LogMananger.repositorySelector was null likely due to error

2010-02-26 Thread Mark Thomas
On 26/02/2010 11:16, Christoph Kukulies wrote: Mark Thomas schrieb: On 26/02/2010 09:47, Christoph Kukulies wrote: I would be glad if I could get some help on m problem getting solved here. http://tomcat.apache.org/tomcat-6.0-doc/config/systemprops.html org.apache.catalina.loader.WebappClassL

Re: log4j :ERROR LogMananger.repositorySelector was null likely due to error

2010-02-26 Thread Christoph Kukulies
Mark Thomas schrieb: On 26/02/2010 09:47, Christoph Kukulies wrote: I would be glad if I could get some help on m problem getting solved here. http://tomcat.apache.org/tomcat-6.0-doc/config/systemprops.html org.apache.catalina.loader.WebappClassLoader.ENABLE_CLEAR_REFERENCES Mark Excuse me,

Re: log4j :ERROR LogMananger.repositorySelector was null likely due to error

2010-02-26 Thread Christoph Kukulies
Mark Thomas schrieb: On 26/02/2010 09:47, Christoph Kukulies wrote: I would be glad if I could get some help on m problem getting solved here. http://tomcat.apache.org/tomcat-6.0-doc/config/systemprops.html org.apache.catalina.loader.WebappClassLoader.ENABLE_CLEAR_REFERENCES Mark Thanks. Gr

Re: log4j :ERROR LogMananger.repositorySelector was null likely due to error

2010-02-26 Thread Mark Thomas
On 26/02/2010 09:47, Christoph Kukulies wrote: I would be glad if I could get some help on m problem getting solved here. http://tomcat.apache.org/tomcat-6.0-doc/config/systemprops.html org.apache.catalina.loader.WebappClassLoader.ENABLE_CLEAR_REFERENCES Mark ---

Re: log4j :ERROR LogMananger.repositorySelector was null likely due to error

2010-02-26 Thread Christoph Kukulies
Pid schrieb: On 26/02/2010 09:47, Christoph Kukulies wrote: I'm turning to this mailing list now after I posted my problem to the Opencms mailing list at opencms.org. And someone from that list gave me a hint that my problem could possibly have something to do with the folling citation: http://

Re: log4j :ERROR LogMananger.repositorySelector was null likely due to error

2010-02-26 Thread Pid
On 26/02/2010 09:47, Christoph Kukulies wrote: I'm turning to this mailing list now after I posted my problem to the Opencms mailing list at opencms.org. And someone from that list gave me a hint that my problem could possibly have something to do with the folling citation: http://mail-archives.

log4j :ERROR LogMananger.repositorySelector was null likely due to error

2010-02-26 Thread Christoph Kukulies
I'm turning to this mailing list now after I posted my problem to the Opencms mailing list at opencms.org. And someone from that list gave me a hint that my problem could possibly have something to do with the folling citation: http://mail-archives.apache.org/mod_mbox//logging-log4j-user/2008

Log4J error using Quartz scheduler

2008-08-12 Thread Brian Parkinson
Hello - Wondering if anyone can help. I am using: - Tomcat 6.0.14 on Linix - Java 1.5.0_13 - Spring 2.5.1 - Quartz scheduler 1.6.0 - commons logging 1.1.1 I am seeing the following in the tomcat catalina-2008-mm-dd.log file: SEVERE: Runtime error occured in main trigger firing loop. java.lang.N

RE: log4j error

2007-11-18 Thread Reich, Matthias
ing/sc.jsp - Matthias -Original Message- From: Caldarale, Charles R [mailto:[EMAIL PROTECTED] Sent: Saturday, November 17, 2007 1:16 AM To: Tomcat Users List Subject: RE: log4j error > From: Steven Crosley [mailto:[EMAIL PROTECTED] > Subject: log4j error > >

RE: log4j error

2007-11-16 Thread Caldarale, Charles R
> From: Steven Crosley [mailto:[EMAIL PROTECTED] > Subject: log4j error > > log4j:ERROR The class "org.apache.log4j.Appender" was loaded by > log4j:ERROR [EMAIL PROTECTED] > whereas object of type > log4j:ERROR "org.apache.log4j.ConsoleAppender" w

log4j error

2007-11-16 Thread Steven Crosley
I'm getting the following error when Tomcat 6.0.14 starts up, and after the the server starts up, I no longer get any messages logged to catalina.out. Can someone tell me what I am doing that is causing this error? log4j:ERROR A "org.apache.log4j.ConsoleAppender" object is not assignable

Re: Re[2]: log4j error! log4j:ERROR Attempted to append to closed appender named.

2007-06-19 Thread Peter
i will try this thanks On 6/20/07, 吴熊敏 <[EMAIL PROTECTED]> wrote: change Append's value 'true' and try again On Wed, 20 Jun 2007 13:18:01 +0800 Peter <[EMAIL PROTECTED]> wrote: > thanks > > but it also generate log file as well. log file can be write. > > i donot know if the error: > > *

Re[2]: log4j error! log4j:ERROR Attempted to append to closed appender named.

2007-06-19 Thread 吴熊敏
change Append's value 'true' and try again On Wed, 20 Jun 2007 13:18:01 +0800 Peter <[EMAIL PROTECTED]> wrote: > thanks > > but it also generate log file as well. log file can be write. > > i donot know if the error: > > *log4j:ERROR Attempted to append to closed appender named > [DEFAULT_

Re: log4j error! log4j:ERROR Attempted to append to closed appender named.

2007-06-19 Thread Peter
thanks but it also generate log file as well. log file can be write. i donot know if the error: *log4j:ERROR Attempted to append to closed appender named [DEFAULT_LOGFILE].* will slow down our system or this error can be ignored? how to solve it thanks On 6/20/07, 吴熊敏 <[EMAIL PROTECTED]> w

Re: log4j error! log4j:ERROR Attempted to append to closed appender named.

2007-06-19 Thread 吴熊敏
I think the configuration of LOG4J has some problems System can't find the log file. On Wed, 20 Jun 2007 12:42:45 +0800 Peter <[EMAIL PROTECTED]> wrote: > hi,all > > we are using log4j under tomcat. and it appeals so many following erros ; > > log4j:ERROR Attempted to append to closed appe

log4j error! log4j:ERROR Attempted to append to closed appender named.

2007-06-19 Thread Peter
hi,all we are using log4j under tomcat. and it appeals so many following erros ; log4j:ERROR Attempted to append to closed appender named [DEFAULT_LOGFILE]. does anyone has an idea why and how to sovle it. thanks ! here is our log4j.xml http://jakarta.apache.org/log4j/"; debug="false">