logging-log4j-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From MCCARTHY Richard <Richard.McCar...@axa-im.com>
Subject RE: log4j and J2EE problem
Date Thu, 09 Aug 2001 08:37:34 GMT
Hi Sandro,

This is what we did for Weblogic 5.1. We created a startup class which was
defined to be the first to be loaded so that logging was always available. 

I think you are right that there will be one VM per clustered box with its
own Log4J singleton.

Richard

-----Original Message-----
From: sandro.ruch@namics.com [mailto:sandro.ruch@namics.com]
Sent: 09 August 2001 07:30
To: LOG4J Users Mailing List
Subject: RE: log4j and J2EE problem



hi,

>>My understanding from the Weblogic documentation,
http://e-docs.bea.com/wls/docs61///programming/packaging.html#1051556, is
that Weblogic uses two classloaders per application.  One for >>EJBs and
one for the webapp with the webapp's class loader being a child of the
EJB's class loader.

>>So, how are people initialing log4j so that there is a single singleton
per application in Weblogic?

>>James

as far as i understand log4j (that's perhaps wrong..??!!) is implemented as
a singleton (1 instance per vm).
so... the question is how many vm are running?? one for web-container and
one for ejb-container?? or one per weblogic-application?
i'm not that far in weblogic 6.1 but in weblogic 5.1 we had to write a
web-logic-startup-class to initialize log4j properly for each
cluster-instance (single-tier-cluster)
and there is only one app running on that cluster...

1 cluster-instance = 1 vm = 1 log4j-instance...?!

any comments?

sandro


---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: log4j-user-help@jakarta.apache.org
This e-mail is confidential and intended only for the addressee(s) shown.
If you are not an intended recipient, please be advised that any use,
dissemination, forwarding or copying of this e-mail is strictly prohibited.
Internet e-mails are not necessarily secure and the AXA Group does not
accept responsibility for changes made to this message after it was sent.
Please note that AXA Investment Managers may monitor incoming and outgoing
electronic mail messages. Should you receive this transmission in error,
notify the sender immediately.  Thank you

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: log4j-user-help@jakarta.apache.org


Mime
View raw message