Weblogic, Java and the Garbage Collector. . . Memory Leak?

We are using weblogic server(6.1) and jdk 1.3.1 for our web application. Java Garbage Collector is not cleaning unused memory even the memory usage is more than 90%. We need to do "force to garbage collection" for every day. The memory usage goes down most of the time once a "force to garbage collection" is done. We believe it to be a memory leak, but can not find the error in the code.  I saw that someone else had posted a similiar question, so I know that we are not alone with this issue.  Any suggestions in where to look or how to stop the issue would be greatly appreciated!

Note : outofmemoryexception error is received in the application if we don't do the "force to garbage collection".

lhunt16Asked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

chimichaelCommented:
We use Jboss v3.2.2 and jdk1.4.1_02 for our application.  The OutOfMemoryException was a familiar problem we had and may be related to yours.  For our situation, we found that memory leaks were coming from not properly closing Connection objects, PreparedStatements, and ResultSets.  
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
mvoelkerCommented:
We had a similar problem with the 6.1 release in the past. BEA support recommended to increase the heap size in the JVM - you'll need to modify the batch/script files to accomplish that. This solved the outofmemory exception problem for us. If it was a memory leak, it would only have increased the intervals between the execeptions, but for us they've completely gone away.

The high memory usage of 90% is not necessarily a result of a memory leak, since weblogic likes to cache a lot for future use.

Regards,

 - michael
0
Mick BarryJava DeveloperCommented:
No comment has been added lately, so it's time to clean up this TA.
I will leave a recommendation in the Cleanup topic area that this question is:

Split between chimichael and mvoelker

Please leave any comments here within the next seven days.

PLEASE DO NOT ACCEPT THIS COMMENT AS AN ANSWER!

objects
EE Cleanup Volunteer
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Java

From novice to tech pro — start learning today.