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 Matthew Bellew :
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 duplicates check in recycl
ing 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 that. I added deb
s R <
> 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
ellew [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 Auth
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.doFi
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 bug that I
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
