I suppose the answer to this question could have been "Try it and find
out". The requests indeed drop through, provided that the "block"
attribute is set to false. The http status code was a 200 by default, but
this was straightforward to override. Additional functionality, such as
redirecting t
Mark,
I browsed the source code for the SemaphoreValve, and it appears that if a
Semaphore cannot be acquired the request will effectively "drop through".
Does that sound accurate? What would I expect in terms of http status code
for the requests that are filtered out?
Thanks,
Bryan
On Tue, Oct
Mark,
Sorry for the delayed response. I had a chance to test out the valve, and
my preliminary testing showed that this worked like a charm for my
application. Thanks for your help.
Bryan
On Tue, Oct 18, 2016 at 9:24 AM, Mark Thomas wrote:
> On 18/10/2016 15:04, Bryan Larson wrote:
> > Good
On 18/10/2016 15:04, Bryan Larson wrote:
> Good morning. I recently posted a question on Stack Overflow that I think
> would be better suited for this group. Here is the question:
> http://stackoverflow.com/questions/40050063/tomcat-max-connections-on-a-per-context-basis.
> To summarize: Besides
