https://issues.apache.org/bugzilla/show_bug.cgi?id=51260
Mark Thomas changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
https://issues.apache.org/bugzilla/show_bug.cgi?id=51240
--- Comment #2 from Mark Thomas 2011-05-25 07:30:50 UTC ---
I agree with Filip's comment re forcing acceptorThreadCount to 1 but I'd still
like to get to the bottom of why the maxConnections limit isn't being enforced.
I'll try and look at
https://issues.apache.org/bugzilla/show_bug.cgi?id=43968
--- Comment #3 from Eiji Takahashi 2011-05-25 09:01:07 UTC
---
Created attachment 27058
--> https://issues.apache.org/bugzilla/attachment.cgi?id=27058
patch for 1.2.30
Patch for 1.2.30.
I did only an easy connection test.
<>
worker.ajp
https://issues.apache.org/bugzilla/show_bug.cgi?id=43968
--- Comment #4 from Eiji Takahashi 2011-05-25 09:01:43 UTC
---
Created attachment 27059
--> https://issues.apache.org/bugzilla/attachment.cgi?id=27059
patch for trunk
Patch for trunk.
I did only an easy connection test.
<>
worker.ajp1.
https://issues.apache.org/bugzilla/show_bug.cgi?id=51240
--- Comment #3 from Tim Whittington 2011-05-25 10:37:48 UTC
---
It looks like there's a race condition between the acceptor thread being
permitted to accept a connection and updating the connection counter.
Two acceptor threads can pass t
https://issues.apache.org/bugzilla/show_bug.cgi?id=51264
Bug #: 51264
Summary: Context/Manager/Store configuration proposal
Product: Tomcat 7
Version: unspecified
Platform: PC
OS/Version: Windows XP
Status: NEW
S
https://issues.apache.org/bugzilla/show_bug.cgi?id=51264
Mark Thomas changed:
What|Removed |Added
Severity|normal |enhancement
--- Comment #1 from Mark
https://issues.apache.org/bugzilla/show_bug.cgi?id=51260
--- Comment #3 from Dan Checkoway 2011-05-25 12:47:17
UTC ---
Mark, from an efficiency standpoint alone, I still think those logical
conditions should be reordered in the code (i.e. don't bother invoking
isHttpToken if separators are allow
