I've encountered a lot of out of memory problems in the past dealing with Websphere Application server. Most have been solved by proper tuning of Websphere settings (heap size,
thread pools etc) or optimization of the applications deployed in it. When finding solutions for those problems, one thing I always read or hear is the suggestion of changing the "paging" settings. Never really understood what its for. What does it have to do with garbage collection and heap settings in Websphere?
Can someone explain this to me in simplest terms?
Is it difficult to tune this? is it more on tuning the server OS settings and not websphere?