|
Question : Websphere Session Management
|
|
We have an application that will sometimes get stuck on a full GC and cause us major issues to the point that the JVM gets hung. We have noticed that this can happen when their are too many session in the heap. There are also several other factors. However, I would like to try and address this one first.
I have talked with the vendor about managing sessions in memory and then issuing a server busy page if it exceeds the thresolds.
The vendor will not implement such a solution. My question is, is there anything I can do in WAS to assist in this effort?
My environment:
WAS 5.1.1.6
JDK 1.4.2_13
We have several JVM that are load balanced.
We do not have session persistance for this application.
Can anyone give me pointers on how to manage sessions outside of a vendors application?
|
Answer : Websphere Session Management
|
|
|
|
|
|
|
