We disabled our LDAP SSO after i noticed on an strace -f -p [pid] of the nodeagent that all spawned threads were making LDAP Calls to the internal authentication server. This opens up other questions, like why would LDAP cause a memory leak in the raw (no applications) Websphere installation.. but at least the memory leak seems to have been solved.
On Wed, Aug 11, 2010 at 2:01 PM, Daniel Tate <daniel.t...@gmail.com> wrote: > Has anyone gotten this to successfully work on SLES11? Other versions > of SLES? Redhat? > > Here is a description from the websphere admin of the problem from his side: > > > > We are running 6.1.0.25 ND on Zlinux (SLES 11). We have 2 nodes created > > on a server with 14 application servers per node. All jvm sizes are set > > to default 50/256. No applications are installed. > > The server has 10GB of real memory and 30GB of swap memory. We start > > the node agents up, then start all applications servers. Once > > everything is up, approximately 7GB of memory is used. > > With the server sitting idle, the memory used by the node agents will > > continue to grow to well over 1GB. Memory will be continuously used > > until all real memory and swap memory is consumed. At this point the > > server becomes unavailable and eventually kills off all java processes > > on the machine. No heap dumps have ever been generated. > > > On Wed, Aug 11, 2010 at 1:27 PM, Daniel Tate <daniel.t...@gmail.com> wrote: >> It's the nodeagents that are consuming the memory. The weird thing is >> RSS and VIRT are both larger than what WAS shows in the console.. and >> VIRT grows even though no swapping was active. >> >> We simply cannot explain the action.. We have PMR's open for every >> possible avenue here. So i'll ask the question another way: >> >> Does anyone have WebSphere (Network Deployment edition) running >> successfully on s390x, SLES11 GA? >> >> >> On Wed, Jul 28, 2010 at 9:05 AM, Agblad Tore <tore.agb...@volvo.com> wrote: >>> and to make it somewhat easier to login :) >>> start just a few servers at boot, then start one at a time until >>> you see problems. >>> Then it's time to stop that last one, and either increase memory >>> or move the not started servers into one or more other Linux machines. >>> >>> >>> ___________________________________________ >>> Tore Agblad >>> Volvo Information Technology >>> Infrastructure Mainframe Design & Development, Linux servers >>> Dept 4352 DA1S >>> SE-405 08, Gothenburg Sweden >>> >>> Telephone: +46-31-3233569 >>> E-mail: tore.agb...@volvo.com >>> >>> http://www.volvo.com/volvoit/global/en-gb/ >>> >>> -----Original Message----- >>> From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Shane >>> G >>> Sent: den 28 juli 2010 02:51 >>> To: LINUX-390@VM.MARIST.EDU >>> Subject: Re: OOM Condition on SLES11 running WAS - Tuning problems? >>> >>> Hmmm - high "sys" CPU usage, high loadavg, system not talking to anyone. >>> Smells like it's busy doing its own stuff. If it were me I'd want to know >>> trends for things like >>> swap-in and swap-out rates, tasks in uninterruptible sleep, context switch >>> counts. >>> >>> SAR is too granular to be any use even if it did have the data. Set up a >>> background script to >>> run top and vmstat and write to disk every so often. A quick bit of awk >>> should show the >>> trend. You could do all the probing of /proc yourself, but I find it easier >>> to allow things like >>> top/ps/vmstat do all the grunt work. >>> >>> Shane ... >>> >>> ---------------------------------------------------------------------- >>> For LINUX-390 subscribe / signoff / archive access instructions, >>> send email to lists...@vm.marist.edu 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 lists...@vm.marist.edu 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 lists...@vm.marist.edu 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/
