Turns out the admins had copied log4j.jar into an endorsed directory (not sure
if it was the Java or Tomcat endorsed)
Removing that jar and restarting Tomcat proved the solution and now logging
blissfully.
Thanks all.
--
David Egan
-Original Message-
From: Maarten Bosteels [mailt
Hi Ceki,
Changing to non-static logger references in EJB is not possible. Too
risky to do so. I will go through the discussion link that you provided
shortly.
Thank you.
Regards,
Wooi Meng
On Thu, Apr 1, 2010 at 8:08 PM, Ceki Gülcü wrote:
> On 01/04/2010 12:41 PM, WM YEOH wrote:
>
>> H
On 01/04/2010 12:41 PM, WM YEOH wrote:
Hi Ceki,
Thank you for the guidance.
I think I better start all over again what was the actual problem to give
you a better picture.
I am currently upgrading the sun one apps server from 7.1 to 9.1 (in UNIX
platform), common-logging.jar, jakar
Hi Ceki,
Thank you for the guidance.
I think I better start all over again what was the actual problem to give
you a better picture.
I am currently upgrading the sun one apps server from 7.1 to 9.1 (in UNIX
platform), common-logging.jar, jakarta-log4j-1.2.6.jar and log4j-1.2.15.jar
are
