Halting JBoss under Cygwin

[Larry W. Virden]

One of the developers trying out Cygwin recently asked me for some assistance regarding the bringing of JBoss to a halt.

Previously, he had been using MKS Toolkit. His process is run a .bat file that starts up the JBoss application server, which also starts his application. Then, under MKS Toolkit, he could use ps and kill to locate the appropriate processes and kill them when he needed.

As he has begun testing JBoss under Cygwin, he has had some problems getting things to work. The first problem was that the processes were not showing up in ps. I found the mention in the ps man page concerning the use of -W to see Windows processes, and that helped some. Now he can see the processes using ps -Wef. However, when he issues a kill against the process id, kill says the process doesn't exist.

Is there some material to which I can point the developer to help him over this hurdle?

Thank you all very much.


     

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

[Marco atzeri-3]

--- Gio 5/11/09, Larry W. Virden  ha scritto:

> One of the developers trying out
> Cygwin recently asked me for some assistance regarding the
> bringing of JBoss to a halt.
>
> Previously, he had been using MKS Toolkit. His process is
> run a .bat file that starts up the JBoss application server,
> which also starts his application. Then, under MKS Toolkit,
> he could use ps and kill to locate the appropriate processes
> and kill them when he needed.
>
> As he has begun testing JBoss under Cygwin, he has had some
> problems getting things to work. The first problem was that
> the processes were not showing up in ps. I found the mention
> in the ps man page concerning the use of -W to see Windows
> processes, and that helped some. Now he can see the
> processes using ps -Wef. However, when he issues a kill
> against the process id, kill says the process doesn't
> exist.
>
> Is there some material to which I can point the developer
> to help him over this hurdle?
>
> Thank you all very much.
>
>

to kill a Windows program use a Windows kill.

http://technet.microsoft.com/en-us/sysinternals/bb896649.aspx

Marco




--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

[Christopher Faylor-8]

On Thu, Nov 05, 2009 at 11:59:04AM +0000, Marco Atzeri wrote:

>
>
>--- Gio 5/11/09, Larry W. Virden  ha scritto:
>
>> One of the developers trying out
>> Cygwin recently asked me for some assistance regarding the
>> bringing of JBoss to a halt.
>>
>> Previously, he had been using MKS Toolkit. His process is
>> run a .bat file that starts up the JBoss application server,
>> which also starts his application. Then, under MKS Toolkit,
>> he could use ps and kill to locate the appropriate processes
>> and kill them when he needed.
>>
>> As he has begun testing JBoss under Cygwin, he has had some
>> problems getting things to work. The first problem was that
>> the processes were not showing up in ps. I found the mention
>> in the ps man page concerning the use of -W to see Windows
>> processes, and that helped some. Now he can see the
>> processes using ps -Wef. However, when he issues a kill
>> against the process id, kill says the process doesn't
>> exist.
>>
>> Is there some material to which I can point the developer
>> to help him over this hurdle?
>>
>> Thank you all very much.
>>
>>
>to kill a Windows program use a Windows kill.
>
>http://technet.microsoft.com/en-us/sysinternals/bb896649.aspx

That shouldn't be necessary if the windows program was started via
cygwin.  If it wasn't started using cygwin then you can use the
/bin/kill -f <windows-pid> to stop it.

cgf

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

[Dave Korn-6]

Christopher Faylor wrote:
> On Thu, Nov 05, 2009 at 11:59:04AM +0000, Marco Atzeri wrote:
>>
>> --- Gio 5/11/09, Larry W. Virden  ha scritto:

>>> processes, and that helped some. Now he can see the
>>> processes using ps -Wef. However, when he issues a kill
>>> against the process id, kill says the process doesn't
>>> exist.

>> to kill a Windows program use a Windows kill.
>>
>> http://technet.microsoft.com/en-us/sysinternals/bb896649.aspx
>
> That shouldn't be necessary if the windows program was started via
> cygwin.  If it wasn't started using cygwin then you can use the
> /bin/kill -f <windows-pid> to stop it.
  ^^^^^^^^^

  There's an implicit subtlety here: cgf wrote the full path to "/bin/kill"
here, because normally if you just type "kill" at the shell you will get the
shell's built-in kill command, which doesn't know the -f option.  Watch out
for that when you try it yourself.

    cheers,
      DaveK



--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple