Re: Barracuda: Patch for Log4jInit servlet

Stefan Armbruster <[email protected]>
Newsgroups gmane.comp.java.enhydra.barracuda.general
Message-ID <[email protected]>
Hi Jake,

see my comments below:
Am Mon, 2003-01-13 um 15.37 schrieb Jacob Kjome:
> Hi Stefan,
> 
> Hmm.....
> 
> That's curious.  When you say "deploying as a .war file" do you mean
> to say that you used catalina's manager deploy command or did you
> create a context that looked something like....
> 
> <Context path="/mypath" docBase="myapp.war" />
I'm using catalina's manager deploy using the ant taskdef. My war
contains a META-INF/context.xml that is properly integrated into
catalina's server.xml.
> 
> I'm not completely sure about what happens to a deployed app when it
> is deployed via Tomcat's manager app since I never do deploys, only
> installs with the manager app.  The latter case where you specify the
> docBas="myapp.war" is, under Tomcat's default settings, is the only
> way to deploy a .war file without expanding the .war to a directory
> structure and then deploying the directory structure.    Can you
> explain how you deployed so that I can reproduce the error.  Sounds
> like it may be a bug in Log4j.
> 
> BTW, are you using the Log4j-1.2.7a.jar from Barracuda/WEB-INF/lib? 
> It isn't an official release, but contains a patch to the entity
> resolver which makes it so that log4j.jar isn't locked after the app
> is Tomcat manager removed from Tomcat.  In the official release of
> logj4-1.2.7, even after a LogManager.shutdown(), the log4j.jar is
> still locked so one can't do a clean build until Tomcat is shut down. 
> It might be good to test both the official release and the unofficial
> logj4-1.2.7a version included in Barracuda.
Currently I'm using 1.2.7a, the one that comes with Barracuda's CVS. I
will try 1.2.7 and report it's behaviort.
BTW: Log4jInit instantiates a DOM parser. Is this a XML parser problem?
I'm using tomcat 4.1.18 LE JDK1.4.

Among other custom jars, these guys are located inside the war:
./WEB-INF/lib/plankton.jar
./WEB-INF/lib/barracuda-contrib.jar
./WEB-INF/lib/barracuda-webapp.jar
./WEB-INF/lib/barracuda-core.jar
./WEB-INF/lib/log4j-1.2.7a.jar
./WEB-INF/lib/barracuda-log4j.jar

In catalina's shared/lib I've put:
./activation.jar
./mail.jar
./xerces-1.4.4-xmlc-2.1.jar
./xmlc-2.1.jar
In catalina's common/lib there's a custom JDBC wrapper driver that uses
log4j. Therefore I have log4j.jar in common/lib too, exactly the same
file like the on in the war. Might the two log4j jar files produce a
conflict? 

> 
> I'll apply your patch on BaracudaMVC.org (once it is up and running)
> since the CVS at enhydra.org will not be updated anymore.
> Jake
> 
> 

Regards,
Stefan

_______________________________________________
Barracuda mailing list
[email protected]
http://www.enhydra.org/mailman/listinfo.cgi/barracuda
FAQ - http://www.jguru.com/faq/Barracuda
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.