I'm using log4j with Allaire's JRun product. I have the log4j-VERSION jar
all set up in the WEB-INF/lib directory with my web app and all seems very
happy and works fine.
Except, when my servlet (from which I'm logging stuff) gets garbage
collected, log4j doesn't seem to want to reinitialize
Ceki,
Thanks for your response; I've done some more digging and discovered the
following behavior.
As I said before when I first start jrun, everything is perfectly fine; if
I touch then my servlet class, causing Jrun to dynamically destroy it and
reload it, this causes log4j to report th
Not that I doubted you...
but you're absolutely right. Switching to log4j-1.2.1.jar fixed my problem;
my servlets are now able to reinitialize the root logger when they're
dynamically reloaded by Jrun.
But does this mean that Jrun is incompatible with the later versions of
log4j? I'm unable