From: Paul Wiggins (pwiggins@cisco.com)
Date: Thu Nov 06 2003 - 10:48:29 EST
Additional info from mpstat and vmstat...
Mpstat shows:
# mpstat 5
CPU minf mjf xcal intr ithr csw icsw migr smtx srw syscl usr sys wt
idl
0 36 0 0 339 238 462 72 0 0 0 664 17 2 0
82
0 1 0 0 298 196 20644 7236 0 0 0 26736 90 9
0 0
0 4 0 0 337 236 17547 6131 0 0 0 22789 88 11
0 0
0 10 0 0 292 190 15199 5115 0 0 0 20113 90 10
0 1
^C#
Vmstat shows:
vmstat 5
procs memory page disk faults
cpu
r b w swap free re mf pi po fr de sr s6 sd -- -- in sy cs us
sy id
0 0 0 5013224 1606072 6 36 1 0 0 0 0 0 1 0 0 239 674 469 17
2 82
82 0 0 3011528 1959360 0 4 0 0 0 0 0 0 0 0 0 192 31188 23817
89 11 0
53 0 0 3011328 1959160 0 4 0 0 0 0 0 0 0 0 0 197 28778 22222
93 6 0
> -----Original Message-----
> From: Paul Wiggins [mailto:pwiggins@cisco.com]
> Sent: Thursday, November 06, 2003 9:10 AM
> To: 'sunmanagers@sunmanagers.org'
> Subject: Java process meltdown after 24hours.... debug???
>
>
> Will summarize. A customer I'm supporting is running Sol8,
> java1. Java(TM) 2 Runtime Environment, Standard Edition
> (build 1.4.1_02-b06) Java HotSpot(TM) Client VM (build
> 1.4.1_02-b06, mixed mode). All patches applied.
>
> Application is a Radius to LDAP proxy (Radius Access Requests
> are converted into LDAP queries). After running for 24-36
> hours... this application causes a CPU hog (jumps from 30%usr to 99%)
>
> Is there anything I can do to debug as an admin. Any java
> command line options that will provide a clue to what
> routines are hogging. The current plan is to stop the Java
> process with a -QUIT option... but not sure that'll result in
> helpful data.
>
> Many thanks for any suggestions.
> -Paul
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 23:27:25 EDT