Marcy, thanks for the pointers. I verified that the thread pool default/max numbers are the same, and the async I/O box remains unchecked. The swap space used stays at 0 for a day or two, but slowly climbs. There are also dips but it never returns to 0 until reboot. The WebSphere java proc grows from 800M to 1200M RES in that time. I suppose it's also possible we have some WebSphere user code that's not behaving as expected.
Ray > -----Original Message----- > From: Linux on 390 Port [mailto:[email protected]] On > Behalf Of Marcy Cortes > Sent: Wednesday, June 23, 2010 11:12 AM > To: [email protected] > Subject: Re: Memory use question > > > It's called a native memory leak. > Lots of things can cause it. > Thread pools, asynci i/o are two areas where this can happen. > See http://www-01.ibm.com/support/docview.wss?uid=swg21368248 > Also http://www-01.ibm.com/support/docview.wss?uid=swg21373312 > > You may have to open a PMR to get IBM to assist. > > Marcy > ---------------------------------------------------------------------- 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/
