At 08:30 09.08.2001 +0200, [EMAIL PROTECTED] wrote:
>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).
I do not adhere to your description. Log4j initializes one default hierarchy at class
load time. However, you can have multiple hierarchies although then it is up to the
user to mange it. It is also possible for log4j to be loaded multiple times in an app
server in which case there will be multiple default hierarchies.
>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?
--
Ceki Gülcü - http://qos.ch
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
