Hello Remy, > --- Ursprüngliche Nachricht --- > Von: Remy Maucherat <[EMAIL PROTECTED]> > This sort of problem is always the same. The component (here, the > realm; earlier, I think it could occur with a valve as well) calls > container.getLogger way too early (and needlessly, as you can see in > the realm code: the containerLog field shouldn't even exist) so the > container logger is created while the main Catalina classloader is set > as the context classloader. So JULI uses the main Catalina logging > configuration. > nice to hear from you. O.K. So this problem is not solvable in JULI/x4juli. Is there a chance to initialize JUL (independently from any other backend) early enough in the bootstrap process? Second: How can we check Tomcat for correct point of log aquiring?
Regards Boris --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
