Sorry for the top post, but no choice with this $%* Notes e-mail client...
Normally, a browser will try to pipeline requests, which means that
multiple requests are sent over a single connection without waiting for
responses. The responses are, however, required to be returned in the
same order as the requests. There are two possibilities I see here:
either 1) the buffering of these separate requests and/or responses is not
release properly, or 2) your browser is never fully consuming some
response off the socket, which leads to retention of the queued responses.
I would suggest you use a packet capture tool like Ethereal (Open Source)
to see what the interaction is at that level while recreating this
problem.
Please respond to "Tomcat Users List"
To: users@tomcat.apache.org
cc:
Subject:Coyote HTTP Connecto memory leak with repeated
sumultaneous requests fro
I am tomcat 4.1.29 as standalone web server with the CoyoteConnector and
the
configuration as follows
I noticed the memory leak if there are multiple repeated requests from
same
browser simultaneously without waiting for response. It is keep
accumulating
the memory and not releasing for eve r(even after the session timeout).
Similar test case with 100 requests ( ran to completion) one after other
is
not leaking any memory.
We are using Synchronized Token while submitting the forms but we are not
using the same in other cases like HTTP/GET.
I ran the tomcat with JProfiler and noticed that the memory leak is
pointing
to org.apache.coyote.http11.InternalInputBuffer.
I used the Tomcat 4.1.31 and still has same problem.
Any help is greatly appreciated.
Thanks and Regards,
Bhakta
--
View this message in context:
http://www.nabble.com/Coyote-HTTP-Connecto-memory-leak-with-repeated-sumultaneous-requests-fro-tf1998241.html#a5485227
Sent from the Tomcat - User forum at Nabble.com.
-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
