SuSE SLES 9 && Java sometimes terminating with SIG_KILL
- From: Matthias Apitz <guru@xxxxxxxx>
- Date: Mon, 11 Sep 2006 11:58:12 +0000 (UTC)
Hello,
We have in this environment:
# cat /etc/SuSE-release
SUSE LINUX Enterprise Server 9 (i586)
VERSION = 9
# uname -a
Linux L000SA03 2.6.5-7.139-bigsmp #1 SMP Fri Jan 14 15:41:33 UTC 2005 i686 i686 i386 GNU/Linux
# /usr/local/j2sdk1.4.2_03/bin/java -version
java version "1.4.2_03"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_03-b02)
Java HotSpot(TM) Client VM (build 1.4.2_03-b02, mixed mode)
from time to time (let's say one in five days) the problem that
the java proc is killed with SIG_KILL (signal 9). It took us some
time to figure it out because the proc is just disappearing and
only starting it with a small shell wrapper made it possible to
catch the exit value of 137 of the proc.
The system has enough real memory:
# dmesg | fgrep -i memory
Memory: 7264160k/8126464k available (2340k kernel code, 74444k reserved, 973k data, 252k init, 6422128k highmem)
and some 16 GByte swap device. Also monitoring the moment of that
with vmstat 5 ... : does not show any problem (the kill happened
between this time frame):
Sa Sep 9 11:14:53 CEST 2006
procs -----------memory---------- ---swap-- -----io---- --system-- ----cpu----
r b swpd free buff cache si so bi bo in cs us sy id wa
0 0 2564 1061448 56884 5586524 0 0 1 1 1 1 2 1 96 1
0 0 2564 1061448 56884 5586524 0 0 11 23 0 0 1 1 98 0
0 1 2564 1057640 57016 5589476 0 0 2 41 0 0 0 2 97 0
1 0 2564 1058216 57028 5589464 0 0 33 21599 0 0 2 1 94 3
0 0 2564 1058312 57032 5589460 0 0 3 58 0 0 2 1 97 0
0 0 2564 1058440 57032 5589460 0 0 7 9 0 0 1 1 98 0
0 0 2564 1058312 57032 5589460 0 0 4 13 0 0 1 1 98 0
0 0 2564 1058440 57032 5589460 0 0 4 9 0 0 1 1 98 0
0 0 2564 1058184 57032 5589460 0 0 8 13 0 0 1 1 98 0
0 0 2564 1058312 57036 5589456 0 0 5 12 0 0 1 1 98 0
0 0 2564 1058312 57036 5589456 0 0 4 30 0 0 1 1 99 0
0 0 2564 1058568 57036 5589456 0 0 8 20 0 0 1 1 97 0
Sa Sep 9 11:15:48 CEST 2006
The peak in 'bo' is caused by some copy in the file system of transaction
logs, triggered by cron, just to mention that.
What can we do to nail this down?
Thx
matthias
--
Matthias Apitz
Manager Technical Support - OCLC PICA GmbH
Gruenwalder Weg 28g - 82041 Oberhaching - Germany
t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211
e <m.apitz@xxxxxxxxxxxx> - w http://www.oclcpica.org/ http://guru.UnixLand.de/
.
- Prev by Date: Re: onboard device discovery
- Next by Date: Re: recvfrom() strange operation
- Previous by thread: Equivalent functions of kernel32 in linux
- Next by thread: env variables
- Index(es):
Relevant Pages
|