i had the same. The database connection pool was not right implemented so each new connection was opened. What you can do is to set the time-out shorter (in the registry, google it) and als to numbers of ports using (up to 60000 or something, also in registry, google it). But better is to find out why so much connections (ports) will be created.
Maarten -----Oorspronkelijk bericht----- Van: Caldarale, Charles R [mailto:[EMAIL PROTECTED] Verzonden: dinsdag 29 november 2005 21:00 Aan: Tomcat Users List Onderwerp: RE: web client running out of ports! (timeout exception) > From: Magyar, Bence [mailto:[EMAIL PROTECTED] > Subject: RE: web client running out of ports! (timeout exception) > > Shouldn't I be getting persistent, reusable connections as the > default with HTTP/1.1? I'm sure you are - but it's the client's responsibility to reuse them; all the server has to do is expect more traffic on the connection, which appears to be what it's doing. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.362 / Virus Database: 267.13.9/185 - Release Date: 28-11-2005 -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.362 / Virus Database: 267.13.9/185 - Release Date: 28-11-2005 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
