Previously I was running tomcat with it's default
thread settings (50 max) and I was getting the errors.
I set the value at 60max and everything's running
smooth. I'm using -server version of hotSpot. I'm glad
I got it to work, but I still think there's a bug in
the VM, or possibly Tomcat.
--- W
On Sat, 17 Mar 2001 00:05:43 +0300, Tagunov Anthony wrote:
>Only don't run in Hotspot mode. Run it in -classic mode.
>Because due to some bug in hotspot compiler the JVM
>crashes with tomcat. It's a recognized Sun's bug and
>funny enough, all the bug reports on that are about
>Tomcat -- a rich co
On Fri, 16 Mar 2001 09:44:46 -0800 (PST), Bill Graham wrote:
>Frank,
>
>Thanks for the reply. I'm going to start tryiong to
>debug Tomcat and see what this NullPointer is.
>Let me know if you get anywhere and I'll do the same.
>
>One thing I've read about and experienced was bad
>performance with
I saw exactly the same thing when I ran a load test on
tomcat 3.2.1 wth jdk 1.2.2_07. What's your Tomcat
max_thread set to? I changed it to 10 and the problem
went away. But I am not happy with the performance
with only 10 threads.
Bill
Bill Graham wrote:
> I'm just getting started with Tomc
Frank,
Thanks for the reply. I'm going to start tryiong to
debug Tomcat and see what this NullPointer is.
Let me know if you get anywhere and I'll do the same.
One thing I've read about and experienced was bad
performance with IBM's vm on Linux w/ Tomcat. You
might want to try Sun's vm and see i
Bill,
I'm doing about the same thing. I'm running the following:
apache 1.3.19
Tomcat 3.2.1
IBMJava2-SDK-1.3-5.0.i386.rpm
classes12.zip (from Oracle)
I am using LoadRunner with a 100 simulated users accessing 9 Oracle JSPs.
I'm running
this 100 times. It fails about 8 out of 10 times.
What i
