Mailingliste - Einträge 2005

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

Re: [qftestJUI] Killing Java server

  • Subject: Re: [qftestJUI] Killing Java server
  • From: Gregor Schmid <Gregor.Schmid@?.de>
  • Date: Wed, 21 Sep 2005 09:02:01 -0000

Hi Bastian,

The problem with "Stop client" is that Windows doesn't properly kill
child processes when the parent is killed. qftestJUI only controls the
Launch Anywhere process, which it kills, but not the JVM started by
it, which obviously survives. For true SUT clients that's not such a
problem, because qftestJUI kills them "from the inside" by forcing
System.exit(), but the registry doesn't have a UI, so it never
connects to qftestJUI.

The question is: How do you stop the registry when not using
qftestJUI? Is there some an additional command, probably also based on
Launch Anywhere, that you can use?

Best regards,

Bastian Bowe <Bastian.Bowe@?.de> writes:

> Hi,
> for my test I need to start a RMIRegistry. After starting it via my Zero G
> Launch Anywhere .exe file from qftest I can't stop it using the stop
> client node. The stop client node is executed and the client "RMIRegistry"
> is removed from the qftest client list. The registry is still running...
> Kind regards
> Bastian

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