Each ear is a separate app in the server's eyes. I believe weblogic is using the equivalent of "multiple" in websphere. That's ok. I'm just wondering whether log4j in multiple classloaders in 1 jvm will have the same log interleaving problem that multilpe jvms has.
thanks -----Original Message----- From: Korver, Aaron [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 02, 2005 4:17 PM To: 'Log4J Users List' Subject: RE: single log file with multiple JVMs vs. multiple class loaders Is each EAR deployed to it's own appserver? Or do both EAR's belong to the same appserver, but fall under different applications? I know that in Websphere there is a setting which says "Application Classloader Policy". The two options are MULTIPLE and SINGLE. If MULTIPLE is choosen, then it will use a seperate classloader per application. Perhaps there is a similar thing for Weblogic? > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Wednesday, March 02, 2005 4:13 PM > To: [email protected] > Subject: RE: single log file with multiple JVMs vs. multiple class > loaders > > > Log4j.jar appears once in each ear file, but not in the war > file at all. > The config file is in a common jar file that is included at > the root of each > ear. Our war file does not contain its own copy of log4j.jar, > log4j.xml/properties, or the common jar. I haven't changed > the default > class loading of weblogic, so I assume the webapp is > inheriting from the app > when it can't find the jar or config files in its own space. > The reason I > think log4j is still getting initialized twice is that I can see a > breakpoint hit in a static block for our log4j wrapper. I > believe it's > happening once in app 1's classloader and once in app 2's classloader. > > thanks > > -----Original Message----- > From: Jacob Kjome [mailto:[EMAIL PROTECTED] > Sent: Wednesday, March 02, 2005 4:07 PM > To: Log4J Users List > Subject: Re: single log file with multiple JVMs vs. multiple > class loaders > > > > Where do you have log4j.jar? Where is the config file you > think is being > used? > Do you have the optional child-first classloading behavior enabled for > webapps or not? > > > Jake > > Quoting [EMAIL PROTECTED]: > > > Hi all, > > > > I'm aware of the problems with more than 1 jvm trying to write to 1 > > file, but what about multiple class loaders? In my j2ee > app we have 2 > > ears, one of which contains a war. They all use the same log4j > > config. They're deployed to WebLogic 8.1. There appears > to be only 1 > > java.exe on my machine (XP Pro), which I believe is for WebLogic, > > regardless of whether I deploy both ears or just 1. (Might > that vary > > by OS or java implementation?) That makes me think there's just 1 > > process writing to the file. However, I think log4j is being > > configured more than once because I see our wrapper class > get loaded > > more than once. Would this cause the same kind of interleaving > > problems that multiple processes will? I haven't seen any > yet, but we > > haven't started testing heavily yet, either. > > > > thanks > > > > > > John Gregg > > Application Systems Engineer > > Wells Fargo Private Client Services Technology > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
