Mailingliste - Einträge 2005

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

Re: AW: [qftestJUI] Thread Dump after catch DeadlockTimeoutException

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

Hi Christian,

you are right, qftestJUI only creates a thread dump for a
DeadlockTimeoutException during an event node, not for any other kind
of node. That's at least a misfeature. We'll fix it with the next

Thanks for bringing this up.

Best regards,

<christian.vollmert@?.de> writes:

> Hi Greg,
> I am using a "Wait for client to terminate" node and I can see the process output, but no Thread dump.
> My question now is, when does qftestJUI produce a Thread dump.
> It seems to me that a Thread dump is produced, if the Deadlock apears during the execution of a MPRC or similar node. If the Deadlock happens during a "Wait for Component" or a Check node, qftestJUI doesn't produce a Thread dump but just reprots a DeadlockTimeoutException.
> Regards,
> Christian
> -----Ursprüngliche Nachricht-----
> Von: Gregor Schmid [mailto:Gregor.Schmid@?.de]
> Gesendet: Montag, 4. Juli 2005 19:06
> An: qftestJUI-list@?.de
> Cc: Vollmert, Christian
> Betreff: Re: [qftestJUI] Thread Dump after catch DeadlockTimeoutException
> 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           
Tulpenstr. 41                                Tel: +49 8171 919870
DE-82538 Geretsried                          Fax: +49 8171 919876