WAS calls non-heap memory "native". That's what you seem to be using up. Look at this http://www-01.ibm.com/support/docview.wss?uid=swg21373312 And if these things don't help, open a PMR with WAS support. Did it stabilize at 18G? The panic_on_oom is a good idea - you can then get a dump (set up a linux dump volume if you are in a hurry - the VMDUMP command takes all day :)
Marcy "This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation." -----Original Message----- From: Linux on 390 Port [mailto:[email protected]] On Behalf Of Daniel Tate Sent: Tuesday, July 27, 2010 7:53 AM To: [email protected] Subject: Re: [LINUX-390] OOM Condition on SLES11 running WAS - Tuning problems? Yes, but no memory ever gets freed. The system stops responding and is too busy dumping information to the console screen to respond to anything at the console or network. And a system-wide panic would provide me with a core file to analyze and send off; though the progress we've made thanks to this group has helped a bit (swappiness = 0) has helped it remain stable longer.. right now we're using 18GB of swap instead of the 35 we were before. i haven't tried panic_on_oom, but thats a good idea and i was braindead not to think of it. On Mon, Jul 26, 2010 at 8:48 PM, Shane G <[email protected]> wrote: > Some more info please. > ... you get a OOM condition ?. > ... the/a large consumer gets killed ? > ... the system "halts" (explain) ?. > > You *want* a system-wide panic ?. If so, setting /proc/sys/vm/panic_on_oom to > "1" will > have the desired effect on non zLinux. > > Shane ... > > On Tue, Jul 27th, 2010 at 1:24 AM, Daniel Tate <[email protected]> wrote: > >> When websphere starts, it consumes all the memory eventually and >> halts, but not panics, the system. > <snip> ... >> At this point i see two problems: >> >> 1) Why is OOM Kill not functioning properly > > ---------------------------------------------------------------------- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO LINUX-390 or visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 > ---------------------------------------------------------------------- > For more information on Linux on System z, visit > http://wiki.linuxvm.org/ > ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/ ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/
