Mailingliste - Einträge 2006

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

Re: [qftestJUI] Apparent deadlock with Qftest and SUT

  • Subject: Re: [qftestJUI] Apparent deadlock with Qftest and SUT
  • From: Karlheinz Kellerer <Karlheinz.Kellerer@?.de>
  • Date: 14 Mar 2006 10:42:46 +0100

Hello Paul,

Deadlocks between qftest and the SUT are encountered from time to time. A
typical reason for those deadlocks is a violation of Swings threadding paradigm
("every GUI action has to be done on the Event-Dispatch-Thread"). The fact that
they show up more likely in combination with qftest is caused by qftests
additional activity on the event-dispatch-thread. But the problem may appear
for other reasons as well.

For "normal" SUT deadlocks, qftest provides a deadlock detection (manual
chapter 15.3.4  Timeouts), but that doesn't work in this case.

To create generate a thread-dump for a more deeper analysis, please perform the
following steps (valid for Windows)

- Perform the steps necessary to get you SUT into the error situation 
  (deadlock, endless loop).

- Open the task manager and find out the process id for your SUT. (On the 
 'application' tab click right on your application and choose 'Switch to process'.
  This leads to a selection of the respective jawaw.exe in the process table...)

- Open a commandline window and go to the 'bin' directory of your qftest.
  installation. There call SendSignal.exe <process id of SUT>.
  Please do this 4 times in about 2 seconds distance.

- The thread dump should then appear in the client terminal which can be opened
  from the Clients menu (or simply by pressing CTRL-T).

Please send the dump in case you need futher help.

Best regards, 

"Paul Bindels" <paul.bindels@?.com> writes:

> We have encountered a problem when we run our product using the Qftest
> application. When we attempt a delete action manually through Qftest the SUT
> GUI freezes. When we perform the same action not under Qftest it works fine.
> If we attempt to record this same action in Qftest, both the SUT and the
> Qftest application freeze up (I then kill the SUT window and Qftest responds
> with "Nothing recorded").
> In an attempt to debug the problem we opened the terminal window of the
> product client in Qftest and attempted to enter a "ctrl-|" ( control pipe)
> to see the thread status. It does not respond ( even though we did not
> launch the SUT in the background with "&" ) with the thread status as can be
> seen when starting from a regular terminal client.
> Have you seen this type of behavior before (SUT/Qft freezing)?
> Is there a way we can see if there is a deadlock when running within Qftest?
> Can we interact with the terminal session once it is started?
> Can jconsole be used to debug this? If so are there any tricks to launching
> it within FTSE?
> Here is the response in the product using ctrl-| (when not run under qftest)
> just prior to pressing the OK button (to the dialog box which performs the
> delete action) causing the gui to freeze:
> Thank you,
> Paul
Karlheinz Kellerer                     Karlheinz.Kellerer@?.de
Quality First Software GmbH