File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
The moose likes Websphere and the fly likes Memory Problem in WAS 3.5 Std Edition Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Products » Websphere
Bookmark "Memory Problem in WAS 3.5 Std Edition" Watch "Memory Problem in WAS 3.5 Std Edition" New topic

Memory Problem in WAS 3.5 Std Edition

Singar Vel

Joined: Aug 22, 2002
Posts: 7
Iam using Websphere 3.5 Standard edition in my application. Actually every 2 to 3 hours webserver is going down. I need to stop and start the server every now and then to make it work.
I think this is because of memory problem. otherwise what could be the reason for this behaviour. How can I get rid of this problem. Please provide me a solution.
Thanks in advance,
Shalini Komarla
Ranch Hand

Joined: Aug 28, 2002
Posts: 59
We were also facing issues with WAS 3.5.4 advanced edition.
You can try and verify if your heap size is increasing constantly. If so, then your code will need to be evaluated. You can use profiling tools like JProbe to help you out with that.
In my case, our application creates a lot of pdf files which was causing degradation in our system performance. On further investigation, we found that IBM's JDK had a bug in it. If you are creating pdf files, then this might be the issue.

Regards,<br />Shalini
Patrick Finnegan
Ranch Hand

Joined: Mar 05, 2002
Posts: 179
Could be this type of problem. Also the default WebSphere install stores session data in memory with overflow on which could in theory exaust the JVM.
An image stream servlet which does not close the url connections it gets to
fetch images can cause an app to hang. If the JVM stack size is large
garbage collection is infrequent and the number of unreferenced objects can
grow to a critical level which can choke the app server. The problem is
more likely to occur in production environments with high performance
capacity machines. The most obvious symptoms are queued Apache connections
displayable via the Apache facility and no response
from the application. The short term solution is to reduce stack sizes to
increase GC frequency. In the long term review the source code to ensure
that unreferenced objects are kept to a minimum.
I agree. Here's the link:
subject: Memory Problem in WAS 3.5 Std Edition
It's not a secret anymore!