-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Henning,
On 2/7/2010 6:26 PM, Henning Blohm wrote:
> I am using JDK logging and I would like to make sure that Tomcat JULI
> does not modify logging runtime configuration that is not owned by
> tomcat or web apps running on tomcat.
>
> Here is what happens:
>
> When adding a standard context and removing it again, it seems that JULI
> resets or modifies otherwise the current logging configuration.
>
> For example: This code:
>
> <code>
> logger.setLevel(Level.INFO);
> logger.info("adding...");
> StandardContext sc = addContext(c);
> logger.info("added");
> System.out.println(logger.getLevel());
> logger.info("removing...");
> removeContext(c,sc);
> logger.info("removed");
> System.out.println(logger.getLevel());
> </code>
Have you tried creating a separate ClassLoader for the purposes of
segregating Tomcat? IF you do that, it's likely that JULI won't reset
your Java logging configuration.
- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAktx48MACgkQ9CaO5/Lv0PB0GgCfdcelHnlaJxHoKQJGj9ay3Xc2
DSYAn1DbCvS2eFmn4JA/+KT3jKeiF3YB
=aSJk
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
