Hi! The client doesn't say anything about the connection, except requesting HTTP/1.1. The tomcat server doesn't either, until the last (100th) response, which suddenly includes a "Connection: Close" header (after which the connection is indeed correctly closed....)
&basa; -----Original Message----- From: Chuck Carson [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 21, 2004 4:33 PM To: Tomcat Users List Subject: RE: Tomcat connection closes after 100 responses --- Shanti Priya <[EMAIL PROTECTED]> wrote: > > Hi !! > In your server.xml file it's set as 100.Check it up. > > -----Original Message----- > From: Bas Alberts [mailto:[EMAIL PROTECTED] > Sent: Tuesday, September 21, 2004 7:54 PM > To: 'Tomcat Users List' > Subject: Tomcat connection closes after 100 responses > > > Hi tomcat users! > > Can anybody answer this question: > Every connection with tomcat is closed after exactly 100 > request/response-pairs. > > Why? > > HTTP/1.1 requests are sent through either a Java socket or a telnet session. > It doesn't matter if the requests and responses are small or large. > It doesn't matter if I set the config. CoyoteConnector attribute acceptCount > to any value. > It doesn't matter if I use @page session="true" or sesion="false". > > Any ideas? > > Bas Alberts > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > Are you explicitly closing you connections in your code, or relying on tomcat for cleanup? -rhugga --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
