You may read more about the log4j error at http://marc.info/?l=log4j-user&m=120897082320333&w=2
So, that seems to be a normal behaviour in Tomcat. Maybe we should conclude that this is an expected side-effect of using antiResourceLocking? :-) On 4/23/08, Caldarale, Charles R <[EMAIL PROTECTED]> wrote: > > From: hezjing [mailto:[EMAIL PROTECTED] > > Subject: Re: Directories in Tomcat 5.5\temp > > > > log4j:ERROR LogMananger.repositorySelector was null likely due to > > error in class reloading, using NOPLoggerRepository. > > Not likely to be the problem, but I can't be sure. > > > 23-Apr-2008 21:06:31 org.apache.catalina.core.AprLifecycleListener > > lifecycleEvent > > INFO: Failed shutdown of Apache Portable Runtime > > This certainly isn't the cause; that's just because you don't have APR > installed. > > - Chuck > > > THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY > MATERIAL and is thus for use only by the intended recipient. If you > received this in error, please contact the sender and delete the e-mail > and its attachments from all computers. > > --------------------------------------------------------------------- > To start a new topic, e-mail: users@tomcat.apache.org > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Hez --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
