Search...
FAQs Subscribe
Pie
FAQs
Recent topics Flagged topics Hot topics Best topics
Search...
Search within WebSphere Search Coderanch
Advance search Google search
Register / Login
advertise on coderanch granny book review grid polymorphism thread boost
  • 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
thread boost book review grid meaningless drivel building better world book advertise on coderanch
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Paul Clapham
  • Ron McLeod
  • Jeanne Boyarsky
  • Tim Cooke
Sheriffs:
  • Liutauras Vilda
  • paul wheaton
  • Henry Wong
Saloon Keepers:
  • Tim Moores
  • Tim Holloway
  • Stephan van Hulst
  • Carey Brown
  • Frits Walraven
Bartenders:
  • Piet Souris
  • Himai Minh

Heap Dump Problem WebSphere Application Server 6.0

 
Arunkumar Subramaniam
Greenhorn
Posts: 8
posted 12 years ago
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
    Send
  • Quote
  • Report post to moderator
Hi Friends

Initial Heap Size 512 MB
Maximum Heap Size : 4 GB
System Ram Size : 8 GB

Heap dump files are generating 2 days once in production server . we are not able to trace the root cause ,we dont know wheather our program problem or application server settings problem

we are getting OutOfMemory in SysErr.log but we dont find any error or exceptions in SystemOut.log

Error Msg :


Thanks
Arunkumar S
 
Joseph Hayes
Greenhorn
Posts: 4
posted 12 years ago
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
    Send
  • Quote
  • Report post to moderator
Not much I can say, I'm afraid, without seeing javacore* and heapdump* files.

What WebSPhere version are you running exactly (run the wasversion script to get that data) The first and most obvious step, then, is to make sure you're on the latest fixpack.

Also, there is often useful informatoin in the FFDC logs. I suggest you sort them by date modified to find the useful ones.

I also suggest you turn on verbose GC to assure that you are not just legitimately running out of heap space.

It APPEARS that this is happening on a new TCP/IP Socket connection (to be clear, this is a guess), so I would concur with conclusions I've seen you make in another forum that this may well be an app server problem. Are you running Stand-alone WAS and running against the web container within the app server?


 
Steve Wink
Ranch Hand
Posts: 225
posted 12 years ago
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
    Send
  • Quote
  • Report post to moderator
This has very good advice on how to diagnose and fix memory problems

http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.express.doc/info/exp/ae/ttrb_mdd4j.html

I've found it useful in finding the problem.
 
Arunkumar Subramaniam
Greenhorn
Posts: 8
posted 12 years ago
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
    Send
  • Quote
  • Report post to moderator
hi friends

i got native_stderr and native_stdout files when Generating a heap file .but there is only out of memory error information, no other information for analyze

native_stderr.log
-----------------
JVMDG217: Dump Handler is Processing OutOfMemory - Please Wait.
JVMDG315: JVM Requesting Heap dump file
JVMDG318: Heap dump file written to C:\IBM\WebSphere\AppServer\profiles\default\heapdump.20090411.121853.7196.phd
JVMDG303: JVM Requesting Java core file
JVMDG304: Java core file written to C:\IBM\WebSphere\AppServer\profiles\default\javacore.20090411.121858.7196.txt
JVMDG274: Dump Handler has Processed OutOfMemory.
JVMST109: Insufficient space in Javaheap to satisfy allocation request
JVMDG217: Dump Handler is Processing OutOfMemory - Please Wait.
JVMDG315: JVM Requesting Heap dump file
JVMDG318: Heap dump file written to C:\IBM\WebSphere\AppServer\profiles\default\heapdump.20090411.121918.7196.phd
JVMDG303: JVM Requesting Java core file
JVMDG304: Java core file written to C:\IBM\WebSphere\AppServer\profiles\default\javacore.20090411.121923.7196.txt
JVMDG274: Dump Handler has Processed OutOfMemory.
etc..
---------------------------

native_stdout.log (only dots(.) )
--------------------------
...............................................................................
................................................................................


Download Log File
------------
http://www.ibm.com/developerworks/forums/servlet/JiveServlet/download/266-264378-14266301-339718/heap%20log.zip

 
Steve Wink
Ranch Hand
Posts: 225
posted 12 years ago
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
    Send
  • Quote
  • Report post to moderator
What about this line:

"JVMDG318: Heap dump file written to C:\IBM\WebSphere\AppServer\profiles\default\heapdump.20090411.121918.7196.phd "

That file should have the information that you need, or one of the other .phd files.
 
Joel Salatin has signs on his property that say "Trespassers will be Impressed!" Impressive tiny ad:
Free, earth friendly heat - from the CodeRanch trailboss
https://www.kickstarter.com/projects/paulwheaton/free-heat
reply
reply
    Bookmark Topic Watch Topic
  • New Topic
Boost this thread!
Similar Threads
More...