Yoav, Originally i placed the log4j1.2.8.jar in the individual webapps /WEB-INF/libs directory. Since i will be deploying the app onto servers that i don't control this is about the only workable solution for me. I did experiment with it in other locations under tomcat/common/lib.
I had thought that with each webapp having its own copy of the log4j jar that they would be independant. But i always seem to get this problem with the second context not working. Lukas > -----Original Message----- > From: Shapira, Yoav [mailto:[EMAIL PROTECTED] > Sent: Friday, 6 June 2003 3:08 a.m. > To: Log4J Users List > Subject: RE: Having LinkageError trouble with log4j under multiple > contexts on Tomcat 4.04 > > > > Howdy, > Where is the log4j.jar located? > > > Yoav Shapira > Millennium ChemInformatics > > > >-----Original Message----- > >From: Lukas Hazlehurst [mailto:[EMAIL PROTECTED] > >Sent: Thursday, June 05, 2003 7:19 AM > >To: Log4j User > >Subject: Having LinkageError trouble with log4j under multiple contexts > on > >Tomcat 4.04 > > > >Hello, > > > >I've been using log4jfor a while now in a fairly basic way (using > chainsaw) > >and it has been fantastic. > > > >My problem now is that i have several identical servlets running under > >tomcat which need to log with different configurations. The problem (a > >common one i believe) is that only the first context is working > properly, > >the second is either silently ignored (if log4j configures itself using > the > >default /classes/lo4j.properties file) or throws up some strange > problems > >(more on this in a second). > > > >I've found this reference to what i think is the same problem i am > having, > >http://marc.theaimsgroup.com/?l=log4j-user&m=105284179922171&w=2 . I > have > >built and deployed the servlet context listener as described. The > context > >listeners work fine, i can trace them starting up and stopping > properly. > >The > >first context loads properly and gets configured nicely, however the > second > >context throws a LinkageError error referring to the 'ErrorHandler' > class > >when it tries to configureAndWatch(). The application then shuts down > after > >the LinkageError. > > > >Both contexts will run fine if the other is removed from the server, so > i > >know that both contexts _should_ work. I have tried moving the log4j > jar > >and > >the context listener jar around into the tomcat lib directory and so on > >(which hasn't helped) but the target server is an ISP server so i don't > >really have that option anyhow. > > > >If anyone has any pointers or something that i've missed, it would be a > >great help. > > > >Log4j: current cvs > >Tomcat: 4.04 > > > >Lukas > >--- > >Outgoing mail is certified Virus Free. > >Checked by AVG anti-virus system (http://www.grisoft.com). > >Version: 6.0.471 / Virus Database: 269 - Release Date: 10/04/2003 > > > > > >--------------------------------------------------------------------- > >To unsubscribe, e-mail: [EMAIL PROTECTED] > >For additional commands, e-mail: [EMAIL PROTECTED] > > > > > This e-mail, including any attachments, is a confidential > business communication, and may contain information that is > confidential, proprietary and/or privileged. This e-mail is > intended only for the individual(s) to whom it is addressed, and > may not be saved, copied, printed, disclosed or used by anyone > else. If you are not the(an) intended recipient, please > immediately delete this e-mail from your computer system and > notify the sender. Thank you. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --- > Incoming mail is certified Virus Free. > Checked by AVG anti-virus system (http://www.grisoft.com). > Version: 6.0.487 / Virus Database: 286 - Release Date: 1/06/2003 > --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.487 / Virus Database: 286 - Release Date: 1/06/2003 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
