At 01:26 PM 1/7/2005 +0100, you wrote: > >Jake, > >Any small test case for me to reproduce this problem? If not, could you >describe the steps I need to take to reproduce it?
I'll get this to you later tonight or tomorrow morning.
Jake
>
>At 09:05 AM 1/7/2005, Jacob Kjome wrote:
>
>>Hi Ceki,
>>
>>I think there may still be something wrong and it shows up when using the
>>ServletContextLogAppender in the logging-log4j-sandbox. Here's some
>>partial log file output. The first comes from a webapp which uses
>>(actively installs using the InitContextListener) the
>>ContextJNDISelector. Notice the Catalina loggers that get added to the
>>repository (along with the JoranConfigurator logger)....
>>
>>log4j:INFO LogManager.getLogger(org.apache.catalina.session.ManagerBase)
>>called
>>log4j:INFO Creating new logger [org.apache.catalina.session.ManagerBase]
>>in repository [default].
>>log4j:INFO
>>LogManager.getLogger(org.apache.catalina.core.ContainerBase.[Catalina].[loc
>alhost].[/contrib-sam])
>>called
>>log4j:INFO Creating new logger
>>[org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/contrib-sa
>m]]
>>in repository [contrib-sam].
>>log4j:INFO Creating new logger [org.apache.log4j.joran.JoranConfigurator]
>>in repository [contrib-sam].
>>log4j:INFO
>>LogManager.getLogger(org.barracudamvc.plankton.data.ObjectRepositoryAssembl
>er)
>>called
>>log4j:INFO Creating new logger
>>[org.barracudamvc.plankton.data.ObjectRepositoryAssembler] in repository
>>[contrib-sam].
>
>[cut]
>
>
>--
>Ceki G�lc�
>
> The complete log4j manual: http://www.qos.ch/log4j/
>
>
>
>---------------------------------------------------------------------
>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]
