Re: Same request object passed to two threads

2016-12-12 Thread Matthew Bellew
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

Re: Same request object passed to two threads

2016-12-08 Thread Mark Thomas
On 08/12/2016 07:32, Violeta Georgieva wrote: > 2016-12-08 3:48 GMT+02:00 Matthew Bellew : >> >> I have narrowed this down quite a lot. This bug is caused by the same >> Http11Processor being pushed on to the recycledProcessors stack twice. I >> discovered this by add a

Re: Same request object passed to two threads

2016-12-07 Thread Violeta Georgieva
> > I will try running our integration server with that set both ways and > > compare. > > > > I don't see how an application bug could cause the same RequestFacade to > > be passed to the webapp on two thread concurrently, however. I'm not > > guessing about t

Re: Same request object passed to two threads

2016-12-07 Thread Matthew Bellew
lt; > chuck.caldar...@unisys.com> wrote: > >> From: Matthew Bellew [mailto:matth...@labkey.com] >> > Subject: Re: Same request object passed to two threads >> >> This should be on the users' mailing list, not dev. >> >> > Just realized that in the cas

Re: Same request object passed to two threads

2016-12-06 Thread Matthew Bellew
lto:matth...@labkey.com] > > Subject: Re: Same request object passed to two threads > > This should be on the users' mailing list, not dev. > > > Just realized that in the case above, I couldn't have hit the quoted > code, > > since neither call to AuthFilter.doFilter() ha

RE: Same request object passed to two threads

2016-12-06 Thread Caldarale, Charles R
From: Matthew Bellew [mailto:matth...@labkey.com] > Subject: Re: Same request object passed to two threads This should be on the users' mailing list, not dev. > Just realized that in the case above, I couldn't have hit the quoted code, > since neither call to AuthFilter.doFilter() had

Re: Same request object passed to two threads

2016-12-06 Thread Matthew Bellew
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

Same request object passed to two threads

2016-12-06 Thread Matthew Bellew
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