Thanks again for squid idea, this is solve my problem. I will use squid
on other web-servers, this is dramaticaly decrease cpu overload.
Byron Miller wrotte:
I use Resin with Apache 1.3.x as well. I've never had
any luck running resin/tomcat by themselves.
I have also had great luck using squid as a
proxy/caching server in front of both. That helped
boost queries per second nicely keeping much of the
tcp over head off the jvm/apache.
--- "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
wrote:
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).
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
