Tal,
I have been testing a similar set up as yours:
Redhat 6.2
Tomcat 3.2.1 w/ bug#1006 fix
IBM 1.3.0 bld cx130-20010207
Linux 2.2.16SMP
I'm testing the throughput of this test server by hammering it
with http requests. The throughput is great, but I'm getting a
ton of NullPointerExceptions on the server and occasionally it
will hang. Now I know that there are some SMP related issues
regarding the stability of the VMs, but IBM claims that they've
been resloved in the build I'm using. Have you (or anyone else)
experienced any behavior like this and if so have you fixed it?
Are you running SMP? I did the same test using a uniprocessor
kernal and got much fewer errors (with a slight hit in speed).
Here's the error:
2001-03-16 08:14:01 - ContextManager: Error reading request, ignored -
java.lang.NullPointerException
at
org.apache.tomcat.service.http.HttpConnectionHandler.processConnection(HttpC
onnectionHandler.java:201)
at
org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoint.java:418)
at
org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java:498)
at java.lang.Thread.run(Thread.java:484)
Using 30 threads with each one making 1000 requests, I get about
500 of these errors.
thanks,
bill
-----Original Message-----
From: Tal Dayan [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, March 28, 2001 8:11 PM
To: [EMAIL PROTECTED]
Subject: RE: Intended use for Tomcat web server
It works great for us.
One of our partners runs a system with Tomcat 3.2.1 standalone for 10 days
now. This server gets about 120K servlet/JSP hits per working day (95% of
them are between 8am and 4pm). We are monitoring it very closely and it is
nothing less than perfect so far.
This is a production system that is open to the
public so it is used with a variety of browsers, platforms, and network
connections.
The server is Linux Redhat 6.2, Celeron 400MHZ, 128KB. The application is
about 100K lines of Java backend code and with about
100 JSP's. The CPU usage gets at most to 5-6% (1 minute average). The JVM is
IBM 1.3.
However, make sure to use a version with a fix for the timeout
issue (http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1006have). Without
this fix, Tomcat 3.2.1 used to hang every day
or two because of dead connections that were not terminated.
We are all grateful here for this great product and you cannot beat the
price.
Tal
> -----Original Message-----
> From: Dave Brown [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, March 28, 2001 1:55 PM
> To: [EMAIL PROTECTED]
> Subject: Intended use for Tomcat web server
>
>
>
> Is the Tomcat Web Server intended for anything other than testing
> purposes?
> It seems to be very reliable from my testing and I was wondering if anyone
> has deployed it in a production environment.
>
> How's it compare to Apache in performance?
>
> Thanks,
>
> Dave Brown
>
>