Well, crud - I don't know what that "j" means. And apparently there
are two different versions of VDT 1.10.1, one at http://vdt.cs.wisc.edu/patches/1.10.1/
and one at http://vdt.cs.wisc.edu/patches/1.10.1-2/. 1.10.1 is
4.0.7 based, and 1.10.1-2 is 4.0.8 based. In either case, I don't see
an axis.jar patch listed in the VDT patchlist.
Also, the globus_4_0_7 and globus_4_0_8 tagged axis.jars appear
identical, with md5sum 36fda08c4a933b9f9231a32609d8ee03 axis.jar
The size looks different for me than it does for you, though: 1448854,
not 1451732.
Alain, any insight?
Charles
On Feb 20, 2009, at 2:29 PM, Steven Timm wrote:
this is vdt 1.10.1j which contains globus 4.0.7
There arre two different instances of axis.jar in
this vdt, both of size 1451732 bytes and dated 5/7/2008.
(they live in $GLOBUS_LOCATION/lib/axis.jar and $GLOBUS_LOCATION/
webmds/WEB-INF/lib/axis.jar)
Steve
On Fri, 20 Feb 2009, Charles Bacon wrote:
On Feb 18, 2009, at 4:59 PM, Steven Timm wrote:
I have seen this problem when trying to use GT 4.0.7 as distributed
by the Open Science Grid VDT, against several different
globus WS hosts, also GT4.0.7 as installed by the VDT. I believe
that it also occurs both earlier and later than that as well.
What's the exact VDT version number? I want to see if it's one
that pulls in a custom axis.jar; I know that has happened in the
past, but does not look like it happens in 1.10.1, which is the
latest. Alternatively, do you see this behavior in 1.10.1 also?
-c
--
------------------------------------------------------------------
Steven C. Timm, Ph.D (630) 840-8525
[email protected] http://home.fnal.gov/~timm/
Fermilab Computing Division, Scientific Computing Facilities,
Grid Facilities Department, FermiGrid Services Group, Assistant
Group Leader.
