On 26/06/17 14:58, Violeta Georgieva wrote:
> 2017-06-26 16:35 GMT+03:00 Mark Thomas :
>>
>> On 26/06/17 14:18, Violeta Georgieva wrote:
>>> 2017-06-26 16:13 GMT+03:00 Mark Thomas :
On 23/06/17 14:47, Violeta Georgieva wrote:
> 2017-06-13 15:44
2017-06-26 16:35 GMT+03:00 Mark Thomas :
>
> On 26/06/17 14:18, Violeta Georgieva wrote:
> > 2017-06-26 16:13 GMT+03:00 Mark Thomas :
> >>
> >> On 23/06/17 14:47, Violeta Georgieva wrote:
> >>> 2017-06-13 15:44 GMT+03:00 Mark Thomas :
> On
On 26/06/17 14:18, Violeta Georgieva wrote:
> 2017-06-26 16:13 GMT+03:00 Mark Thomas :
>>
>> On 23/06/17 14:47, Violeta Georgieva wrote:
>>> 2017-06-13 15:44 GMT+03:00 Mark Thomas :
On 13/06/17 11:05, Violeta Georgieva wrote:
> 2017-06-13 13:04
2017-06-26 16:13 GMT+03:00 Mark Thomas :
>
> On 23/06/17 14:47, Violeta Georgieva wrote:
> > 2017-06-13 15:44 GMT+03:00 Mark Thomas :
> >> On 13/06/17 11:05, Violeta Georgieva wrote:
> >>> 2017-06-13 13:04 GMT+03:00 Violeta Georgieva :
>
>
On 23/06/17 14:47, Violeta Georgieva wrote:
> 2017-06-13 15:44 GMT+03:00 Mark Thomas :
>> On 13/06/17 11:05, Violeta Georgieva wrote:
>>> 2017-06-13 13:04 GMT+03:00 Violeta Georgieva :
java.lang.NullPointerException: null
>>
>> Appears to be the same
Hi,
2017-06-13 15:44 GMT+03:00 Mark Thomas :
>
> On 13/06/17 11:05, Violeta Georgieva wrote:
> > 2017-06-13 13:04 GMT+03:00 Violeta Georgieva :
> >>
> >> Hi,
> >>
> >>
> >> 2017-06-12 21:43 GMT+03:00 Mark Thomas :
> >>>
> >>> On 09/06/17
On 13/06/17 11:05, Violeta Georgieva wrote:
> 2017-06-13 13:04 GMT+03:00 Violeta Georgieva :
>>
>> Hi,
>>
>>
>> 2017-06-12 21:43 GMT+03:00 Mark Thomas :
>>>
>>> On 09/06/17 16:26, Violeta Georgieva wrote:
2017-06-09 17:25 GMT+03:00 Mark Thomas
2017-06-13 13:04 GMT+03:00 Violeta Georgieva :
>
> Hi,
>
>
> 2017-06-12 21:43 GMT+03:00 Mark Thomas :
> >
> > On 09/06/17 16:26, Violeta Georgieva wrote:
> > > 2017-06-09 17:25 GMT+03:00 Mark Thomas :
> >
> >
> >
> > >> I've spent some
Hi,
2017-06-12 21:43 GMT+03:00 Mark Thomas :
>
> On 09/06/17 16:26, Violeta Georgieva wrote:
> > 2017-06-09 17:25 GMT+03:00 Mark Thomas :
>
>
>
> >> I've spent some time working through the various possible combinations
> >> of events and have concluded it is
On 09/06/17 16:26, Violeta Georgieva wrote:
> 2017-06-09 17:25 GMT+03:00 Mark Thomas :
>> I've spent some time working through the various possible combinations
>> of events and have concluded it is impossible to completely fix this
>> without imposing additional requirements
Hi,
2017-06-09 17:25 GMT+03:00 Mark Thomas :
>
> On 09/06/17 12:41, Mark Thomas wrote:
> > On 05/06/17 09:38, Violeta Georgieva wrote:
> >
> >
> >
> >> Try with this test
> >>
https://github.com/violetagg/tomcat/commit/53564d4e73496cb3badcaaab81a1314cf2ed750d
> >
> > Thanks.
On 09/06/17 12:41, Mark Thomas wrote:
> On 05/06/17 09:38, Violeta Georgieva wrote:
>
>
>
>> Try with this test
>> https://github.com/violetagg/tomcat/commit/53564d4e73496cb3badcaaab81a1314cf2ed750d
>
> Thanks. That clarifies things a lot.
>
> It boils down to what should happen when an I/O
On 05/06/17 09:38, Violeta Georgieva wrote:
> Try with this test
> https://github.com/violetagg/tomcat/commit/53564d4e73496cb3badcaaab81a1314cf2ed750d
Thanks. That clarifies things a lot.
It boils down to what should happen when an I/O error occurs reading
from the request or writing to the
Hi,
2017-06-02 23:44 GMT+03:00 Mark Thomas :
>
> On 02/06/2017 10:46, Violeta Georgieva wrote:
> > 2017-06-02 12:37 GMT+03:00 Mark Thomas :
> >>
> >> On 02/06/2017 10:23, Violeta Georgieva wrote:
> >>> Hi Mark,
> >>>
> >>> 2017-05-22 14:28 GMT+03:00 Mark Thomas
On 02/06/2017 10:46, Violeta Georgieva wrote:
> 2017-06-02 12:37 GMT+03:00 Mark Thomas :
>>
>> On 02/06/2017 10:23, Violeta Georgieva wrote:
>>> Hi Mark,
>>>
>>> 2017-05-22 14:28 GMT+03:00 Mark Thomas :
>>
>>
>>
I'm leaning towards thinking this is an
2017-06-02 12:37 GMT+03:00 Mark Thomas :
>
> On 02/06/2017 10:23, Violeta Georgieva wrote:
> > Hi Mark,
> >
> > 2017-05-22 14:28 GMT+03:00 Mark Thomas :
>
>
>
> >> I'm leaning towards thinking this is an application bug.
> >>
> >> If the application has two
On 02/06/2017 10:23, Violeta Georgieva wrote:
> Hi Mark,
>
> 2017-05-22 14:28 GMT+03:00 Mark Thomas :
>> I'm leaning towards thinking this is an application bug.
>>
>> If the application has two non-container threads, A and B, then, as per
>> section 2.3.3.4 of the Servlet
Hi Mark,
2017-05-22 14:28 GMT+03:00 Mark Thomas :
>
> On 10/05/17 20:50, Violeta Georgieva wrote:
> > Hi,
> >
> > 2017-05-02 12:54 GMT+03:00 Violeta Georgieva :
> >>
> >>
> >> 2017-05-02 12:25 GMT+03:00 Mark Thomas :
> >>>
> >>> On 02/05/17
On 10/05/17 20:50, Violeta Georgieva wrote:
> Hi,
>
> 2017-05-02 12:54 GMT+03:00 Violeta Georgieva :
>>
>>
>> 2017-05-02 12:25 GMT+03:00 Mark Thomas :
>>>
>>> On 02/05/17 09:52, Violeta Georgieva wrote:
Hi,
I have a question about Async state
Hi,
2017-05-02 12:54 GMT+03:00 Violeta Georgieva :
>
>
> 2017-05-02 12:25 GMT+03:00 Mark Thomas :
> >
> > On 02/05/17 09:52, Violeta Georgieva wrote:
> > > Hi,
> > >
> > > I have a question about Async state DISPATCHING.
> > >
> > > I have the following
2017-05-02 12:25 GMT+03:00 Mark Thomas :
>
> On 02/05/17 09:52, Violeta Georgieva wrote:
> > Hi,
> >
> > I have a question about Async state DISPATCHING.
> >
> > I have the following scenario
> > - Application invokes startAsync() and then continues processing in a
> > separate
On 02/05/17 09:52, Violeta Georgieva wrote:
> Hi,
>
> I have a question about Async state DISPATCHING.
>
> I have the following scenario
> - Application invokes startAsync() and then continues processing in a
> separate non-container thread A.
> - At some point thread A makes dispatch() -> Async
Hi,
I have a question about Async state DISPATCHING.
I have the following scenario
- Application invokes startAsync() and then continues processing in a
separate non-container thread A.
- At some point thread A makes dispatch() -> Async state is changed to
DISPATCHING
- At the same time a socket
23 matches
Mail list logo