Bug 5546

Summary:	Endorsing Xerces/Xalan in tomcat
Product:	Java WS Core	Reporter:	Tom Scavo <trscavo@gmail.com>
Component:	globus_wsrf_core	Assignee:	Rachana Ananthakrishnan <ranantha@mcs.anl.gov>
Status:	ASSIGNED
Severity:	normal	CC:	jwscore-dev@globus.org
Priority:	P3
Version:	4.0.4
Target Milestone:	---
Hardware:	All
OS:	All

Description From Tom Scavo 2007-09-11 08:33:16

In share/globus_wsrf_common/tomcat/tomcat.xml, only xalan.jar is deployed into
tomcat's endorsed directory.  In fact, all the files in
$GLOBUS_LOCATION/endorsed should be deployed into tomcat's endorsed directory. 
See the following message thread for details:

http://www.globus.org/mail_archive/gt-user/2007/07/msg00178.html

------- Comment #1 From Rachana Ananthakrishnan 2007-10-05 09:53:32 -------

Tom,

In my 4.0 branch install, I only see xalan.jar in $GLOBUS_LOCATION/endorsed and
the tomcat script copies that to the right location.

In trunk install, I see 3 jars in $GLOBUS_LOCATION/lib and those are copied
correctly on a tomcat deploy too.

Are you seeing different behavior when you deploy 4.0.4 ?

Rachana

------- Comment #2 From Tom Scavo 2007-10-05 10:12:51 -------

(In reply to comment #1)
> 
> In my 4.0 branch install, I only see xalan.jar in $GLOBUS_LOCATION/endorsed and
> the tomcat script copies that to the right location.

That's a bug.  OpenSAML requires all three JARs.

------- Comment #3 From Rachana Ananthakrishnan 2007-10-05 12:59:32 -------

We haven't seen any issues with this in Java WS Core. The OpenSAML jar is used
by the SAML Authorization callout code and the tests for that work fine with
only xalan.jar in endorsed directory. Maybe your install requirements need
these additioanl jars in endorsed?

------- Comment #4 From Tom Scavo 2007-10-05 13:15:33 -------

If something else besides the required versions of Xerces/Xalan are endorsed in
Tomcat, I can almost guarantee you'll see problems eventually.  Some tomcats
come with endorsed versions of Xerces/Xalan with a known memory leak that will
cause tomcat to crash under load.  I have seen this reported time and time
again in the Shibboleth mailing lists.  The only versions of Xerces/Xalan that
are known to be stable are the ones that ship with GT 4.1.x.

------- Comment #5 From Tom Scavo 2007-10-05 13:26:12 -------

BTW, I don't think you can automate the endorsement of Xerces/Xalan in tomcat. 
If there are *other* versions of Xerces/Xalan already endorsed in tomcat
(especially tomcat 5.0.x), these must be removed before endorsing the versions
of Xerces/Xalan that ship with GT 4.1.x.  I'm afraid it's a manual process.  It
can not be automated.