Setting maxKeepAliveRequests=1 seems to fix the issue as well. Perhaps the
problem has something to do with keep alive requests? Any other thoughts?
Mike
Filip Hanik - Dev Lists wrote:
turn off keep alive for your profiler to not give you false positives
maxKeepAliveRequests=1
turn off keep alive for your profiler to not give you false positives
maxKeepAliveRequests=1
Connector port=8080 protocol=HTTP/1.1 maxKeepAliveRequests=1
connectionTimeout=2
redirectPort=8443 /
On 02/03/2010 02:14 PM, youngm wrote:
(This is a new thread
(This is a new thread spawned from my Tomcat 6.0.24 Google Chrome thread
with better information)
I'm running Tomcat 6.0.24, Sun JDKx86 6u18, Windows 7 64, Firefox and Chrome
browser.
I've noticed that for about the first 1-3 min after my tomcat instance has
started some of my requests that
