mod_jserv/5785: mod_jserv creates 80 TIME_WAIT sockets -- why ? Is this a bug ?

[Thierry Delaitre <de...@cpc.wmin.ac.uk>]

>Number:         5785
>Category:       mod_jserv
>Synopsis:       mod_jserv creates 80 TIME_WAIT sockets -- why ? Is this a bug ?
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    jserv
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Sun Feb 20 06:10:00 PST 2000
>Closed-Date:
>Last-Modified:
>Originator:     delaitt@cpc.wmin.ac.uk
>Release:        Apache 1.3.11
>Organization:
apache
>Environment:
SunOS rhino.cscs 5.7 Generic_106541-08 sun4m sparc SUNW,SPARCstation-20
>Description:
I noticed that mod_jserv creates a number of sockets which have TIME_WAIT status,
though mod_jserv is working properly. I get 80 sockets with TIME_WAIT status on
Solaris 7 and this number settles down to 80. Please find a subset of the
"netstat -a" output below.

Could you please let me know if this is behaviour is normal and why the number
of sockets settles down to 80. I don't recall this huge number of sockets
when using Apache-1.0

I would be grateful for any info.

Thanks,

Thierry.

localhost.8007             *.*                0      0     0      0 LISTEN
localhost.8007       localhost.46985      32768      0 32768      0 TIME_WAIT
localhost.8007       localhost.46987      32768      0 32768      0 TIME_WAIT
localhost.8007       localhost.46988      32768      0 32768      0 TIME_WAIT
localhost.8007       localhost.46989      32768      0 32768      0 TIME_WAIT
localhost.8007       localhost.46990      32768      0 32768      0 TIME_WAIT
localhost.8007       localhost.46991      32768      0 32768      0 TIME_WAIT
localhost.8007       localhost.46992      32768      0 32768      0 TIME_WAIT
localhost.8007       localhost.46993      32768      0 32768      0 TIME_WAIT
localhost.8007       localhost.46994      32768      0 32768      0 TIME_WAIT
localhost.8007       localhost.46995      32768      0 32768      0 TIME_WAIT

>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:
 [In order for any reply to be added to the PR database, you need]
 [to include <ap...@Apache.Org> in the Cc line and make sure the]
 [subject line starts with the report component and number, with ]
 [or without any 'Re:' prefixes (such as "general/1098:" or      ]
 ["Re: general/1098:").  If the subject doesn't match this       ]
 [pattern, your message will be misfiled and ignored.  The       ]
 ["apbugs" address is not added to the Cc line of messages from  ]
 [the database automatically because of the potential for mail   ]
 [loops.  If you do not include this Cc, your reply may be ig-   ]
 [nored unless you are responding to an explicit request from a  ]
 [developer.  Reply only with text; DO NOT SEND ATTACHMENTS!     ]