This discussion is archived
3 Replies Latest reply: May 9, 2013 2:00 PM by 1006613 RSS

JVM Crashes

1006613 Newbie
Currently Being Moderated
Environment - Processor - AMD 64bit, OS - Solaris, Java 1.6.0.22b 64 bit.

Problem - We have a native application calling a Java application. The native application loads the input data from data files in memory and processes this data. This application is working fine all these days without any issue. Recently the input data size has grown drastically. This is is causing a JVM crash "Segment Fault". When the application is executed, it always fails on the Java block just before initalizing the actual object that processes the data. Essentially, Java is not working on any data until this point but it fails just before initializing the object.

When we run the same scenario with -Xint java args, we don't see the exception anymore but there is a failure down somewhere else and surprisingly it fails with JNI exception "Segment Fault". We don't expect a Java/JNI exception here as this part of code doesn't make any JNI call and moreover the JVM destroy call is successful before reaching this point.

We are looking for some help in identify this issue and possible resolution to the same.

Thanks in advance
  • 1. Re: JVM Crashes
    gimbal2 Guru
    Currently Being Moderated
    Try with a more recent version of Java I'd say. A more recent version of Java 6 at the very least.

    And I hope you can hire some expert assistance to support you. If you have any kind of question which can be answered in a forum, which tends to require something actually visible like code, feel free to ask it. But it needs to be a question that can be answered by Java developers and I'm sorry to say even though you're trying to hook into the Java virtual machine - all you are basically going to be able to offer is gobs of C++ code which you won't get very far with here.
    We don't expect a Java/JNI exception here as this part of code doesn't make any JNI call
    You're running this from a native application aren't you? So you're using the Java Native Interface, only in the reverse direction (the invocation API). You even posted this in the JNI forum so you must have realized it in some way or another. Its not too strange to get a JNI exception, although its hard to say anything definitive since you refuse to share the actual error you're getting.
  • 2. Re: JVM Crashes
    jschellSomeoneStoleMyAlias Expert
    Currently Being Moderated
    user2114451 wrote:
    as this part of code doesn't make any JNI call
    Is there any JNI calls at all in any way up to that point? If so then it is suspect.
    Is there any dll initialization code at all associated with the JNI including third party libraries? If so then it is suspect.
    and moreover the JVM destroy call is successful before reaching this point.
    At least in the past that did nothing with the Oracle/Sun VM.
  • 3. Re: JVM Crashes
    1006613 Newbie
    Currently Being Moderated
    We tried the most recent version of Java6 (1.6.0.45) & Java7 (1.7.0.21)
    We don't see the issue anymore with Java7 but we see intermittent results with Java6.

    Anyways, we would upgrade to Java7 which is more consistent. Thanks for you help.

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points