Win a copy of Head First Android this week in the Android forum!
  • 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:
  • Tim Cooke
  • Campbell Ritchie
  • Paul Clapham
  • Ron McLeod
  • Liutauras Vilda
Sheriffs:
  • Jeanne Boyarsky
  • Rob Spoor
  • Bear Bibeault
Saloon Keepers:
  • Jesse Silverman
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
Bartenders:
  • Piet Souris
  • Al Hobbs
  • salvin francis

How to troubleshoot a memory leak or an out-of-memory exception in the Weblogic Server

 
Ranch Hand
Posts: 2234
Eclipse IDE Firefox Browser Redhat
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi Ranchers , Please tell me how to ?

How to troubleshoot a memory leak or an out-of-memory exception in the Weblogic Server



I know my question is vague .
A General idea on this is sufficient . Please help
 
best scout
Posts: 1294
Scala IntelliJ IDE Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi Ravi,

a log message containing the corresponding OutOfMemoryException would be a good starting point ;-)

Additionally you could use a profiler to analyze the memory usage of your application to spot a memory leak in the results. Perhaps you can track down the problem even with simple tools like jconsole or jvisualvm together with the server logs to narrow the part of your application causing the memory leak by watching which actions in the application are consuming so much memory.

Marco
 
Ravi Kiran Va
Ranch Hand
Posts: 2234
Eclipse IDE Firefox Browser Redhat
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Thanks Macro ,

The approach you mentioned(Using Proflers ) would be fine before check in into Repository . Now situation is out of my hand .

While Googling i found that

"You can also troubleshoot the outofmemory(OOM) or server
hanging issues by taking a thread dump of the server. "


Can you please tell me what is Thread Stuck mean ?
 
Marco Ehrentreich
best scout
Posts: 1294
Scala IntelliJ IDE Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Most popular JVMs support startup parameters which enable some kind of heap dump even when the JVM shuts down with an OutOfMemoryException. Then you can try analyze this dump with a profiler later.

Moreover at least Sun's JDK comes with additional tools (jmap, jstack, etc.) which allow you to create stack traces and memory dumps from a running JVM.

Possibly Websphere gives some support here, too, but I unfortunately don't know very much about it.

But to be honest, if you don't know what all these things are it's very unlikely that you will find the necessary information in such a dump. Anyway good luck ;-)

Marco
 
Ranch Hand
Posts: 884
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Ravi Pavan wrote:The approach you mentioned(Using Proflers ) would be fine before check in into Repository . Now situation is out of my hand .



The OOM is typically caused by a piece of code in your application. So you cannot have a situation whereby it is out of your hand. Even if that piece of code is deployed to production and you found that it is causing the memory leak, you have got to fix it and release it.

Ravi Pavan wrote:Can you please tell me what is Thread Stuck mean ?


A thread will execute a request and by default, WLS will set a pre-determined duration, 600 seconds, as the threshold for the thread to finish the work. If for whatever reasons, the thread doesn't complete its work within 600 seconds, it is deemed to be "stucked" by WLS. This is however, just, an information/warning. There is a possibility that the thread cannot finish its work or it could be that the thread needs more time to finish its work. Looking through the logs, you may find that the thread becomes unstucked later on. Or if you don't, something is wrong. Look into the code that the thread is running, you may have to fix some bad coding or a bad design.
 
Ravi Kiran Va
Ranch Hand
Posts: 2234
Eclipse IDE Firefox Browser Redhat
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
You are right . Thanks .
 
You showed up just in time for the waffles! And this tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop
https://coderanch.com/wiki/718759/books/Building-World-Backyard-Paul-Wheaton
reply
    Bookmark Topic Watch Topic
  • New Topic