Hi Curt,
What does the following mean?...
On 1/1/2009 8:27 PM, Curt Arnold wrote:
liUse per-application copies of log4j, that is remove log4j.jar from
WEB-INF/lib./li
The first part says use per-application copies of log4j and then it says that
is remove log4j.jar from WEB-INF/lib. From my
On Jan 2, 2009, at 12:04 PM, Jacob Kjome wrote:
Hi Curt,
What does the following mean?...
On 1/1/2009 8:27 PM, Curt Arnold wrote:
liUse per-application copies of log4j, that is remove log4j.jar
from
WEB-INF/lib./li
I think I cut and pasted from suggestions on the mailing list. Tomcat
You are most likely encountering a known Tomcat bug where unloaded
classes can be inadvertently used during static initialization of
other classes. There is a patch for Tomcat which has been integrated
into Glassfish, but there has been no action to integrate it into
Tomcat. If you can't
Hi all,
I'm note sure, if this is a log4j issue but maybe you can give me a clue
where to look. Actually I want to update from Velocity 1.4 to 1.6. This
means I have to update some other libraries too including
commons-logging. I'm using now log4j 1.2.15 and commons-logging-1.1.1.
After
Hello Thoralf,
The problem you are facing is probably related to the clean up code
Tomcat invokes when it redeploys web-apps. Replace commons-logging.jar
with jcl-over-slf4j.jar and your problem will go away. You need to add
slf4j-api.jar and slf4j-log4j.jar to you class path (in addition to
Hi,
yes, that works. Great - thanks!
bye
Thoralf
Ceki Gulcu schrieb:
Hello Thoralf,
The problem you are facing is probably related to the clean up code
Tomcat invokes when it redeploys web-apps. Replace commons-logging.jar
with jcl-over-slf4j.jar and your problem will go away. You need to
