This appears to fix the problem. We are pushing to our integration server,
and hope to update our supported technologies page soon.
Thanks all,
Matt
On Thu, Dec 8, 2016 at 1:09 AM, Mark Thomas wrote:
> On 08/12/2016 07:32, Violeta Georgieva wrote:
> > 2016-12-08 3:48 GMT+02:00 Matth
ss() does not check the return result from
connections.remove(). Maybe
a) ConnectionHandler.process() should only call release(processor) if the
connections.remove(socket)==processor?
or
b) release(socket) shouldn't call recycledProcessors.push()?
Matt
On Tue, Dec 6, 2016 at 3:53 PM, Matt
#x27;m not guessing
about that. I added debugging code to my app and managed to stop in the
debugger, and I could see two http-nio-8080-exec- threads with the same
object.
Matt
On Tue, Dec 6, 2016 at 2:58 PM, Caldarale, Charles R <
chuck.caldar...@unisys.com> wrote:
> From: Matthew B
Just realized that in the case above, I couldn't have hit the quoted code,
since neither call to AuthFilter.doFilter() had returned.
I can build and debug Tomcat, so any advice would be very welcome.
Matt
On Tue, Dec 6, 2016 at 2:20 PM, Matthew Bellew wrote:
> I have an intermittent
I have an intermittent bug that I've been trying to trying to track down
for a long time. The symptom is that the same tomcat request object is
being processed by two different threads. The symptom is a random crash
when one thread returns and recycles the request, and the other thread
access the
