Performance tuning and OutOfMemoryError(OOME)

For the past few days, I have been trying to find out the cause for OOME occuring in our application. In the rigorous web-searching that followed, I have found lot many sites/blogs/bug-databases which were helpful in deciding our next approach to be taken to resolve OOME.

It is after we started to see lot many OOMEs that we started worrying seriously about nailing down the application to find memory leaks. The profiler tool we used did not provide any lead either… It was then that I started to search web to see if someone was in our shoes earlier. Fortunately, there have been many and some have suggested workarounds for such problems. Below are some of the URLs that are worth browsing. Hope these enlighten u into tuning ur application to improve its availability.

Configuring heap, internal workings of the Garbage Collector and JVM are a must when you are deploying a critical application that requires a high degree of availability and a good performance. All the very best in finetuning ur app… So get set go….

Info abt GC

Blogs… ( Read under the section : Your Web App is leaking memory during restarts – Here’s why…)

BUGS filed;:YfiG?bug_id=4697804


~ by WYSIWYG on December 15, 2005.

2 Responses to “Performance tuning and OutOfMemoryError(OOME)”

  1. Thanks a million for the wonderful links on Performance Tuning in Java.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: