[logback-user] tomcat configuration - jndi selector initialization printed three times

[Ceki Gülcü]

Hi Markus,

ContextSelectors intervene during logger retrieval. However, since 
logback-access does not have a notion of loggers, ContextSelectors do 
not work with logback-access. You could use filters to separate logs per 
web-app.

As for status information appearing twice, do you have both a status 
listeners and debug set to true in your config file?

Cheers,
--
Ceki

On 25/01/2011 9:06 PM, Markus Meisters wrote:
> Hi,
>
>
>> Logback-access requires the Tomcat valve. Are you confusing
>> logback-access and the JNDIContextSelector?
>
> I want to get access log and webapplications (with jndi separation) running.
>
>> The latter is a logback-classic feature and independent of logback-access.
>> Is there a copy of slf4-api.jar or logback-classic.jar in your web-app?
>
> not that I'm aware of :} because the goal also was to avoid to have tem within the app, but will check again.
>
> btw. wenn I deploy the logback-demo webapp within the tomcat6 I see the message 2 times
>
> Could this be related to threads?
>
> Many thanks in advance
> Markus