FWIW, TSM is the Tivoli Storage Manager, a backup service similiar to
Veritas' NetBackup. It is possible (entering the realm of pure speculation
here; I am not a backup engineer, let alone a Tivoli backup engineer) that
if the TSM agent died in the middle of a backup, that it may have left the
OS in an unstable condition.
HTH,
Ian
It's better to be hated for who you are
than loved for who you're not
Ian D. Stewart
Distributed Computing Engineer II
DSS eCommerce Engineering
JPMorganChase Global Technology Infrastructure
Phone: (614) 244-2564
[EMAIL PROTECTED]
thsolutions.com
To
08/17/2006 06:24 "Maven Users List"
PM <[email protected]>
cc
Please respond to Subject
"Maven Users Re: Maven java processes refusing
List" to die
<[EMAIL PROTECTED]
he.org>
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" <[email protected]>
To
"Maven Users List" <[email protected]>
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.
-----------------------------------------
This transmission may contain information that is privileged,
confidential, legally privileged, and/or exempt from disclosure
under applicable law. If you are not the intended recipient, you
are hereby notified that any disclosure, copying, distribution, or
use of the information contained herein (including any reliance
thereon) is STRICTLY PROHIBITED. Although this transmission and
any attachments are believed to be free of any virus or other
defect that might affect any computer system into which it is
received and opened, it is the responsibility of the recipient to
ensure that it is virus free and no responsibility is accepted by
JPMorgan Chase & Co., its subsidiaries and affiliates, as
applicable, for any loss or damage arising in any way from its use.
If you received this transmission in error, please immediately
contact the sender and destroy the material in its entirety,
whether in electronic or hard copy format. Thank you.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
