Tomcat is multithreaded - ie. lots of connections -> one process, while
Apache forks lots of processes, and when a process dies it takes it's waited
connections too. Just a different design.
Unless it's causing you problems I wouldn't worry about it.
Cheers... Mike
> -----Original Message-----
> From: Martin Holmgren [mailto:[EMAIL PROTECTED]]
> Sent: 27 October 2000 16:39
> To: '[EMAIL PROTECTED]'
> Subject: TIME_WAIT socket buildup problem in Tomcat
>
>
> Hi!
>
> I have noticed that Tomcat leaves a new TCP-socket in the
> TIME_WAIT-state
> for quite a while after each request to a servlet or jsp.
> When I send many
> requests to my server, this causes a massive buildup of
> sockets that are
> "blocked" for quite some time, until the server finally goes
> down, when
> the number of open sockets exceeds its max value.
>
> How can I work around this? I've compared with how Apache
> serves static
> pages, and it never leaves any sockets in TIME_WAIT. Is there
> a reason for
> that difference, or is it just that Apache currently has a
> more elegant
> solution to the problem?
>
> Thanks in advance!
>
> /Martin Holmgren
>
>
>
>
>
