[slf4j-user] slf4j with jboss

[Ceki Gülcü]

Hello Asi,

I think the problem you are referring to was due to a classloader
objects held to by Jakarta commons-logging (JCL). In recent versions
of *Tomcat* the problem does not occur because Tomcat explicitly
invokes clean up methods in JCL when it recycles web-applications. I
do not know if Jboss does the same.

SLF4J does not suffer from the same problem because it does not hold
class loader references.

At 03:36 PM 12/22/2006, you wrote:
>Hi,
>
>I would like to ask if anyone aware of a problem while
>using slf4j with jboss application server.
>
>Few years ago, when we tried to use "commons logging",
>we had the following problem: when deploying new war
>over existing one (while the other was running), the
>logger was "stuck" and after the deployment it didn't
>work.
>Therefore, for every update we had to stop the server
>and start it again.
>I the end we used log4j only.
>
>Is anyone aware of that problem with slf4j?
>
>Thanks,
>Asi

-- 
Ceki Gülcü
Logback: The reliable, generic, fast and flexible logging framework for Java.
http://logback.qos.ch