I've never seen "classloader bleed" in any version of the JDK, and that's
been an area of interest of mine ever since I wrote on the subject (see the
Papers at www.javageeks.com).
That said, I'm not at all sure what problem you're running into. One trick I
use a lot, particularly for production deployments, is to create a
standalone JRE co-located with the Tomcat installation, so that you're not
affected by any other Java-related install into the "global" JRE installed
on a Win2k box in C:\Program Files\java\j2re.... I've got a paper on this up
at javageeks.com, too: "Multiple JRE Homes".
The "endorsed" directory hack in JDK 1.4.0 is something I'll just not get
into now.... ;-)
Ted Neward
Architect, UCDavis Account & Financial Services
http://www.javageeks.com
http://www.clrgeeks.com
-----Original Message-----
From: Heitzso [mailto:heitzso@xxxxxxxxxxxxx]
Sent: Saturday, July 27, 2002 11:48
To: axis-user@xxxxxxxxxxxxxx
Subject: re class loader - dll hell
I've spent another 12 hours or so fighting what I thought
was a class loader bleed through under winXX. The exception
I was seeing was a SAX parser message re
"INIT" missing trailing "</INIT>".
Hence I assumed class loader bleed through w/ xerces or
1.4.0_01 jvm built in xml parser. One reason I assumed that
is the proliferation of xml parsers that were in the env
(jvm, tomcat, WEB-INF/lib) of various and asundry versions.
THE FIX: reboot WinXX box and retry. I also pulled all xerces
jars from our WEB-INF/lib, but that by itself didn't make
the problem go away.
So there's some nasty bug in combo:
Win2K
sun 1.4.0_01
tomcat 4.0.4
axis beta 3
that can leave garbage in memory until the box is rebooted.
Note I did check win task manager to insure the java process
had truely died -- it had -- problem still persisted until
reboot. I _assume_ either JVM corrupted system memory or
a dll was loaded that didn't go away until reboot.
Note that Debian Linux unstable and Red Hat 7.3 with same mix
sun 1.4.0_01, tomcat 4.0.4, axis beta 3
doesn't have the problem.
BTW, my jar config:
tomcat 4.0.4 common/lib left alone (nothing added or removed)
axis jars (all) copied to appropriate WEB-INF/lib
no xerces copied to WEB-INF/lib
no java.endorsed.dirs set
The reboot fix was tested and confirmed on two systems, both Win2k.
Heitzso
|
