• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Memory Leak in WebSphere

 
Ranch Hand
Posts: 127
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hello Kyle and Others,
My Websphere(Production enviornment) have to restarted againafter nearly 10-15 days. I have checked database connections in Resource analyser. But it appeared ok.
But I don't know where is the memory leak ???
How can one know about memory leak ??

Thanks in advance
Please help...
I
[ May 11, 2002: Message edited by: Bhiku Mhatre ]
 
author
Posts: 3892
5
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Bhiku,
The best tools for finding a memory leak are profiling tools like JInsight (from Alphaworks) or JProbe (from Sitraka). You will need to set up a stress test and look for your leak using these tools.
Kyle
 
Ranch Hand
Posts: 34
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I see that it's been a long time since this was posted, but just incase anyone is looking for a problem I found with WebSphere v5.0.2 and came across this by google search I'll go ahead and post.


I found that WebSphere v5.0.2 running on AIX 5.1 had a memory leak in it's ibmorb.jar that would never release entries that it stored in an internal cache. IBM had to do a hot fix for my client and as far as I know this was not made publicly available. It will probably be fixed by IBM in their WAS 5.1 release. The scenario where this arises is when one application makes a remote EJB call to another application. The IBM ibmorb.jar does not release references to the EJB stubs and will continue to amass references until your server instance eventually encounters an OutOfMemoryError.


Here is the explanation from IBM:


1.The Problem analysis for the Defect 74270 is as below:


The identityHashTable was holding references to objects (stubs) , thus
preventing Garbage collection of objects. This happens especially
when the EJB from a different jar file is being accessed by a servlet
in a different ear file.


2.The Problem resolution for the same as below:
Replaced identityHashtables with weakHashMaps.

-Ed
 
Bhiku Mhatre
Ranch Hand
Posts: 127
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Thanks Ed.
My application is still running WAS 4.07. The memory leaks we faced were our won creation and not WAS specific.
Thanks a lot for info any way. The app should migrate to WAS 5.x soon.
 
reply
    Bookmark Topic Watch Topic
  • New Topic