I suspect the problem relates to pipelining of HTTP 1.1 requests over a single persistent TCP connection. Pipelining is intended to improve efficiency, allowing the need for multiple images to present a web page be expressed to a web server one after another, before any of the responses are given. However, the responses must be presented in the same order as the requests, and therein lies your problem. If your short running request is issued over the same TCP connection as one of the earlier, yet to be responded to, long running requests, the response to the later request must wait for the earlier request to be responded to first. In this scenario, you need to get either the browser or the web server to stop using persistent connections. Of course, this may make it less efficient for serving up "normal" web pages.
Please respond to "Tomcat Users List" <users@tomcat.apache.org> To: "'Tomcat Users List'" <users@tomcat.apache.org> cc: Subject: RE: No of concurrent requests per session I'm guessing this is more of a browser issue. If you're using IE, I seem to recall there is a registry entry that lets you set the maximum concurrent requests. George Sexton MH Software, Inc. http://www.mhsoftware.com/ Voice: 303 438 9585 > -----Original Message----- > From: Abhilash Kumar [mailto:[EMAIL PROTECTED] > Sent: Monday, February 13, 2006 6:43 AM > To: Tomcat Users List > Subject: No of concurrent requests per session > > Hello: > > I am using Tomcat 5.0.30 with HTTP 1.1 Connector. If I try > to make a third request while two other request's (which i > have already made) responses have not yet arrived, then > Tomcat is not serving the request until one of the pending > response arrives. This limits me to only two pending requests > (irrespective of the webapp) at a time. > > My front app is like a dashboard which integarates multiple > web apps of which some are reporting apps which requires 4 to > 7 minutes to process a request and some are data processing > apps which requires only seconds to process the request. > Assume the user clicks on two reporting links which open up > as new windows from the main app window. Now when he clicks > on another link irrespctive of the webapp, nothing happens > until one of the reporting request's response is arrived. > This problem appears only if the requests belong to the same session. > > Any pointers / advices will be greatly appreciated. > > thanks and regards, > > -- Kannan. > > > > -------------------------------------------------------------- > Amritha Institute of Medical Sciences, Cochin, India > Sent using "PostMaster" by QuantumLink Communications > One Internet account, unlimited personal e-mail addresses > Get your free copy of "PostMaster" at http://www.mailserve.net/ > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
