Dear Olaf,
Thanks for answer. I found the following:
If I use Tomcat or Resin only, the server always broken with large
queries. In the Tomcat manager I found that there are many thread with
'S' status with long time.
I analize these threads with 'netstat -anp' command from linux prompt. I
found these connections in 'CLOSE_WAIT' status. This is present that,
the client don't answer the CLOSE status, when the server send the
answer out (for e.g. close the browser before full answer arrive).
My solution:
I put front of the Tomcat an Apache2 with jk2 and these problem is
solved. With Apache2 the answer times is better too than Tomcat alone.
Before it the CPU usage was 50-90%, now only 1-10%. From the Apache I'm
cache static contents (gif, html, css etc. - I have many items from it),
and I think the Apache serve the static contents too, better than Resin
or Tomcat.
Regards,
Ferenc
Olaf Thiele wrotte:
Hi Ferenc,
does the error happen only with your own servlet or
did you experience it with the standardized interface?
Furthermore, you report on NullPointers. Where exactly
do they happen. The printstacktrace should tell you that.
This would be a good starting point.
Hope this helps
Olaf
