Funny, we've recently had kind of the opposite problem -- recurring SIGSEGV
problems during CruiseControl-initiated maven builds on a linux platform (CC
2.5, Maven 2.0.4, Sun JDK 1.5.0_07-b03 on a RH CentOS 3.7 SMP Intel box). It
was a rare occurrence until this week, now every build breaks due to the
seg. fault. :-/

It's interesting how nervous I feel without the CI green light. Tomorrow we
get to set up a new CI build machine to (hopefully) remedy the situation.

Anyway, just sharing a bit of misery.

Cheers,
Doug

On 8/17/06, [EMAIL PROTECTED] <
[EMAIL PROTECTED]> wrote:

I saw this recently.  It turned out to be caused (how I don't know) by a
service that had died on the server in the middle of the night.    The
service was the "TSM Scheduler Service".   This is on a Windows Server.

Wayne Naccari
(205) 437-6464



Mike Perham <[EMAIL PROTECTED]>
08/17/2006 04:29 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 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 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.
>



-----------------------------------------
This e-mail and any attachments are intended only for the
individual or company to which it is addressed and may contain
information which is privileged, confidential and prohibited from
disclosure or unauthorized use under applicable law.  If you are
not the intended recipient of this e-mail, you are hereby notified
that any use, dissemination, or copying of this e-mail or the
information contained in this e-mail is strictly prohibited by the
sender.  If you have received this transmission in error, please
return the material received to the sender and delete all copies
from your system.


Reply via email to