We've been using Sun's JDK 1.3.1 on Linux for a while now.
Currently we use Tomcat 3.2.1 and xerces version 1.3.0.
It seemed to work fine on RedHat 6.1 but on 7.1 there was a link that missing.
I think I experienced the same seg fault issue that is referred to below.
If this is the problem it can be fixed by doing the following as root:
cd /lib/i686
The required link is "libpthread.so". If it isn't there then create it:
ln -s libpthread.so.0 libpthread.so
Then run:
/sbin/ldconfig
This fixed the problem with regards to running 1.3.1 on RedHat Linux 7.1.
Hope this helps.
P.
On Wed, 27 Jun 2001 11:33:37 -0400
"Jeffrey Lam" <[EMAIL PROTECTED]> wrote:
JL> Switching to IBM's JDK 1.3 solved my problem of the HttpConnectionHandler not
JL> being able to start. Thank you!
JL>
JL> I was using Sun's JDK 1.3.0_02 and my problem arose when I upgraded to Sun's
JL> JDK1.3.1
JL>
JL> Thanks again!
JL>
JL> ----- Original Message -----
JL> From: "pete" <[EMAIL PROTECTED]>
JL> To: <[EMAIL PROTECTED]>
JL> Cc: <[EMAIL PROTECTED]>
JL> Sent: Wednesday, June 27, 2001 0:58
JL> Subject: Re: Tomcat won't start with j2sdk 1.3.1 & Linux
JL>
JL>
JL> > I get this. It sucks.
JL> >
JL> > The issue, for me at least, stems from the fact that i am running a
JL> > Struts project, and i need to override the jaxp.jar classes with xerces
JL> > parser classes.
JL> >
JL> > I previously did this by putting a jar named 0xerces.jar in the lib/
JL> > folder of my tomcat install, which worked fine, since those classes
JL> > loaded before the ones specified in jaxp.jar.
JL> >
JL> > This worked great with IBM's JDK1.3.0 - never used Sun's 1.2.2 on Linux.
JL> >
JL> > However, since 'upgrading' to Sun's JDK1.3.1 with Hotspot, the JVM
JL> > segfaults when tomcat starts up, giving the same error you describe.
JL> >
JL> > I'm not sure why this happens, but maybe 1.3.1 doesn't like having its
JL> > classes overridden.
JL> >
JL> > There are 2 ways around this - invoke the JVM with the '-classic'
JL> > switch, thus disabling the JIT, or to remove 0xerces.jar from lib/,
JL> > which breaks my Struts projects.
JL> >
JL> > The third solution is not to use the JDK1.3.1 at all, and stick with the
JL> > IBM JDK, which is my current course of action.
JL> >
JL> > Hope this helps, and i hope you find a better solution than i did.
JL> >
JL> > -Pete
JL> >
JL> >
JL> >
JL> >
