There seems to be a problem with the Tomcat 4.0.1 class loader. I have figured out
how to get around it, but am posting it in case anyone else runs into it, or someone
wants to fix it.
I have an application that works fine with Tomcat 3.2.x but when I ran it under 4.0.1
I would get a ClassFor
A while ago I posted a question about a segmentation fault error I was getting with
Tomcat. The machine is SuSE Linux 7.1 and the application was fine with J2SDK 1.3 but
when I switched to J2SDK 1.3.1 it aborted with a segmentation fault. It turns out
that it was aborting in the call to new D
I have had luck with Tomcat and Xerces by putting an underscore in front of xerces.jar
(i.e., calling it _xerces.jar) and putting it into the $TOMCAT_HOME/lib directory with
the rest of the jar files. The shell script that generates the CLASSPATH puts them in
alphabetical order (as Chris McNei
Should I take the complete lack of any feedback on this subject to mean that no one
has tried Tomcat/Linux/j2sdk 1.3.1?
--- Forwarded message from Douglas E. Hornig ---
>Date: 15 Jun 2001 12:45:17 EDT
>From: Douglas E. Hornig
>Subject: Tomcat won't start with j2sdk 1.3.1 &
Has anyone run Tomcat under linux with j2sdk 1.3.1-b24? I have been using Tomcat
3.2.1 (and now 3.2.2) happily for some time now with j2sdk 1.3 and linux (SuSE 7.1,
kernel 2.4.5). I decided to get current with my Java VM, but when I try to start up
Tomcat I get this error:
/usr/local/tomcat/
I have run into a strance performance problem with Tomcat that I am at a loss to
figure out. In a nutshell, when I run Tomcat (version 3.2.1, standalone) on a Solaris
Sparc server and hit it with a Windows client, the minimum response time is is abount
0.2 seconds. This is for a simple servle
