Mailingliste - Einträge 2005


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [qftestJUI] Thread Dump after catch DeadlockTimeoutException


  • Subject: Re: [qftestJUI] Thread Dump after catch DeadlockTimeoutException
  • From: Gregor Schmid <Gregor.Schmid@?.de>
  • Date: Mon, 04 Jul 2005 17:12:01 -0000

Hello Christian,

if qftestJUI is able to create a thread dump, you'll always find it in
the process output of the SUT which is located in the run-log directly
after the "Start (Java) SUT client" node and also after the respecive
"Wait for client to terminate" node. So if you not only kill the SUT
in case of a deadlock but also add a wait for terminate node you
should have the thread dump right there.

Best regards,
    Greg

<christian.vollmert@?.de> writes:

>    Hi everybody,
>
>    I got the following problem: Due to some problems with our Eventqueue
>    it happens form time to time that the SUT ends up in a Deadlock. I've
>    built a workaround using a try-catch block and simply restarting the
>    SUT.
>
>    The Problem with this is, that I don't get a thread-dump in the
>    protocol anymore.
>
>    Anybody got an idea how to catch a DeadlockTimeoutException and still
>    get a Thread dump in the runlog?
>
>    Thanks,
>    Christian

--
Gregor Schmid                                Gregor.Schmid@?.de
Quality First Software GmbH                     http://www.qfs.de
Tulpenstr. 41                                Tel: +49 8171 919870
DE-82538 Geretsried                          Fax: +49 8171 919876


Videos Downloads Dokumentation Kaufen Gratis Testen