tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark Thomas <>
Subject Re: svn commit: r1476761 - in /tomcat/trunk/java/org/apache/catalina/core:
Date Sun, 28 Apr 2013 18:03:30 GMT
On 28/04/2013 15:01, Konstantin Kolinko wrote:
> 2013/4/28 Konstantin Kolinko <>:
>> 2013/4/28 Mark Thomas <>:
>>> On 28/04/2013 14:19, wrote:
>>>> Author: markt
>>>> Date: Sun Apr 28 13:19:48 2013
>>>> New Revision: 1476761
>>>> URL:
>>>> Log:
>>>> Improve logging by naming the Servlet that hasn't stopped.
>>> I'm currently looking at the trunk unit test failures with buildbot. I'm
>>> not at all sure what is going on. The logs suggest threads are getting
>>> stuck for extended periods of time (minutes in some cases) but it always
>>> seems to happen with the same tests.
>>> The delays are too long for GC but they could be swapping related as
>>> buildbot is running on a VM. If that were the case I'd expect to see
>>> more variation in the test failures though.
>>> At the moment I am looking at improving the logging which has the added
>>> benefit of being useful to our users as well.
>>> What I really need is the ability to trigger a thread dump from within
>>> the JVM. While there are ways of doing it, none of them are particularly
>>> simple. I might look into this if the logging doesn't get me anywhere.
>>> Suggestions - and better still help - welcome.
> 1.
>> There exists Thread.getStackTrace()  @since 1.5 that can get
>> stacktrace from a different thread.
>> I thought it could be a good addition to our WebAppLoader report of
>> non-stopped threads.
>> There exists static method Thread.getAllStackTraces(): Map<Thread,
>> StackTraceElement[]>.


> 2. Maybe change default logging configuration to use OneLineFormatter.
> It will give us thread names in the log,
> Alternatively, there appears to be a way to customize the pattern used
> by SimpleFormatter
> ("Cannot apply simpleformtatter pattern to" thread from Jan 2013)
> 3. "Read time out" errors
> What is strange is that the whole Tomcat startup and shutdown appears
> to be faster
> than timeout value reported by client thread
> (read fails after 12 and 9 seconds and Tomcat goes up and down in 10 and 7).

The read fails after 3s. The 12s and 9s figures are for the entire test.

> 4.
> says
> "java.lang.IllegalStateException: Calling [asyncDispatch()] is not
> valid for a request with Async state [MUST_COMPLETE]"
> There is no such message in NIO test.

Haven't looked into this yet but it looks possible this might have the
same root cause.

Fundamentally, the VM running the tests appears to have quite big IO
delays. This is triggering failures in some timing related tests.

I suspect there isn't much we can do about this short of buying new
hardware. I'll stick my infra hat on and take a look at the VM host.


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message