• 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

Help understanding JVM Crash Dump file

 
Greenhorn
Posts: 18
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

I am using JNI to run some native code from Java. The code runs fine in Windows XP system. When i port the code to Linux and try running it there, It runs perfectly for 2-3 times. And after that it crashes. This crash is so random that it crashes the first time sometimes. Sometimes it works for 2-3 times and then crashes.

As the code is running fine for some time, the problem may be with the memory.

My Java Memory Arguments are "-Xms 768m -Xmx1024m".
Java Version : 1.6.0_12 and I am running my application in Weblogic 11g.

Every time it crashes, it gives me a JVM crash dump file, from which I am not able to decode the problem.

Here is the latest crash dump file:


Can anyone help me to locate the reason for these random crashes ? Is the problem with Heap Memory as some of the statics say the memory space is 99% used ?
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
reply
    Bookmark Topic Watch Topic
  • New Topic