August 10, 2011 11:26 AM
>> Subject: Re: TC 6.0.20 Cleanup after application crash
>>
>> Hi Chris,
>>
>> I did indeed read and digest Mark's email and talked to the vendor about
>> that issue. The stack trace on the old blog post is from the one Mark
>
You may want to check first which "keep alive" settings they have for the whole
chain.
If one of them happened to be close to 15 minutes, that might be a strong hint.
Another tool is "netstat", to see exactly in which TCP state these persistent connections
find themselves in. (another bad sente
- Original Message -
> From: Dante Bell
> To: Tomcat Users List
> Cc: Christopher Schultz
> Sent: Wednesday, August 10, 2011 11:26 AM
> Subject: Re: TC 6.0.20 Cleanup after application crash
>
> Hi Chris,
>
> I did indeed read and digest Mark's emai
On 10/08/2011 19:26, Dante Bell wrote:
> after 15 minutes it starts serving up db responses!
Sounds a bit like an OutOfMemoryError, which is not uncommon during load
tests.
If the 'customised' load tester is a bit rough around edges, what are
you really testing?
p
-
Hi Chris,
I did indeed read and digest Mark's email and talked to the vendor about
that issue. The stack trace on the old blog post is from the one Mark
was helping out with (man, that was a really bad sentance!).
This is a different issue :( I don't have a stack trace and I don't have
access to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dante,
On 8/10/2011 11:57 AM, Dante Bell wrote:
> We are seeing that after an application crash (customized load
> tester with minimal error handling so it crashes often)
When you say "crash", do you mean you get a stack trace in the logs and
Tomcat
