On 10.07.2011 16:07, Mark Thomas wrote:
> On 10/07/2011 14:53, Rainer Jung wrote:
>> Using an AccessLogValve during the unit tests reveals, that the thread
>> name in the request processor is often not set when handliung async
>> requests.
>>
>> To reproduce run TestAsyncContextImpl for trunk with
On 10/07/2011 14:53, Rainer Jung wrote:
> Using an AccessLogValve during the unit tests reveals, that the thread
> name in the request processor is often not set when handliung async
> requests.
>
> To reproduce run TestAsyncContextImpl for trunk with test.accesslog=true
> and have a look at the a
Using an AccessLogValve during the unit tests reveals, that the thread
name in the request processor is often not set when handliung async
requests.
To reproduce run TestAsyncContextImpl for trunk with test.accesslog=true
and have a look at the access log in output/build/logs. The only
requests lo