We've been doing some load testing with WAS on RHEL4 under VM, and the other day something weird came up.
The machine is defined with 1.3 gb. storage under zVM 5.2, and about 1.5 gb. swap space in two partitions: One about 1 gb. (dasdf), and the other about .5 gb. (dasdd) We use a product called "Teamquest" to monitor the system during the test, and as we were running, it suddently reported "dasdf" was 100% full. WAS started to choke, and analysis of a crashdump appeared to show threads hung consistent with malloc failures. We've been going around trying to figure out: 1) why we suddenly should have run out of virtual memory (if we did, because we never even got close to that before), and 2) why it was reported in this way. Does anyone know if there's anything in the swap space management mechanism that would cause Linux to fail malloc if a single swap partition fills up? Is there some kind of process affinity for paging to swap spaces? -------------------------------------------------------- If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/ -------------------------------------------------------- ---------------------------------------------------------------------- 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
