The only time I see rogue maven processes is when our unit tests fork and I
kill the main maven process. The child unit test maven instance continues
to run until the unit tests are complete.
I have seen this too (not sure if this unit tests fork or not) after
pressing STRG-C on the
to Subject
Maven UsersRe: Maven java processes refusing
List to die
[EMAIL PROTECTED]
he.org
kill -9 PID is not doing it.I've logged out and logged in again , still
no luck.Now I have 2 maven java processes
one eating away 1.6G of memory and the other 204M.These 2 dudes are just
refusing to die
This is on Linux machine.
--
Jeff Mutonho
GoogleTalk : ejbengine
Skype:
Reboot?
The only time I see rogue maven processes is when our unit tests fork and I
kill the main maven process. The child unit test maven instance continues
to run until the unit tests are complete.
mike
Jeff Mutonho [EMAIL PROTECTED] wrote on 08/17/2006 12:24:30 PM:
kill -9 PID is not
PM
Please respond to
Maven Users List users@maven.apache.org
To
Maven Users List users@maven.apache.org
cc
Subject
Re: Maven java processes refusing to die
Reboot?
The only time I see rogue maven processes is when our unit tests fork and
I
kill the main maven process. The child unit
to
Maven Users List users@maven.apache.org
To
Maven Users List users@maven.apache.org
cc
Subject
Re: Maven java processes refusing to die
Reboot?
The only time I see rogue maven processes is when our unit tests fork and
I
kill the main maven process. The child unit test maven instance
