Results 1 to 13 of 13
  1. #1
    ragav123 is offline Member
    Join Date
    May 2010
    Posts
    4
    Rep Power
    0

    Default JVM crash in Linux

    Hi,
    The following error occurred when our application ran in a Linux Server. The RAM capacity is 64GB. The application used only 15GB at the time of crash. So, there should not be a memory issue. The jdk version is jdk1.6.0_03. Can anyone of suggest what would be reason for this error and what can be done to overcome this.
    #
    # An unexpected error has been detected by Java Runtime Environment:
    #
    # SIGSEGV (0xb) at pc=0x0000002a95af6a4e, pid=27143, tid=1177815392
    #
    # Java VM: Java HotSpot(TM) 64-Bit Server VM (1.6.0_03-b05 mixed mode)
    # Problematic frame:
    # V [libjvm.so+0x474a4e]
    #
    # An error report file with more information is saved as hs_err_pid27143.log
    #
    # If you would like to submit a bug report, please visit:
    # HotSpot Virtual Machine Error Reporting Page
    #

    Some more details
    o Operating system and its specification
    Linux version 2.6.9-89.0.9.ELlargesmp (mockbuild@x86-002.build.bos.redhat.com) (gcc version 3.4.6 20060404 (Red Hat 3.4.6-11)) #1 SMP Wed Aug 19 08:12:11 EDT 2009
    o Processor details
    Intel(R) Xeon(R) CPU E7330 @ 2.40GHz
    o Memory
    64GB RAM

  2. #2
    masijade is offline Senior Member
    Join Date
    Jun 2008
    Posts
    2,571
    Rep Power
    9

    Default

    What is in the file "hs_err_pid27143.log"?

  3. #3
    ragav123 is offline Member
    Join Date
    May 2010
    Posts
    4
    Rep Power
    0

    Default

    We dont have the file with us. But which would have caused this sudden JVM crash? In most of the forums, they say it is JVM issue, In some, they say Processor Issue.

  4. #4
    masijade is offline Senior Member
    Join Date
    Jun 2008
    Posts
    2,571
    Rep Power
    9

    Default

    That log will give you more information. Without that you're only guessing.

  5. #5
    Tolls is offline Moderator
    Join Date
    Apr 2009
    Posts
    12,224
    Rep Power
    20

    Default

    All we can say is there was a segmentation fault (null pointer by the looks of it) in the JVM, but whether that was you, the JVM, or the system we can't say.

  6. #6
    ragav123 is offline Member
    Join Date
    May 2010
    Posts
    4
    Rep Power
    0

    Default

    I have attached "hs_err_pid27143.txt" log you have asked. I went through the log. But it has lot of memory details which I cant understand. Hope anyone of you can understand and confirm where the issue is.
    Attached Files Attached Files

  7. #7
    masijade is offline Senior Member
    Join Date
    Jun 2008
    Posts
    2,571
    Rep Power
    9

    Default

    All I can really do is to point you here, and, of course, the link in the error itself.

    The document above is 1.5, but somewhere in the same area should be an equivalent for 1.6, and that document itself is still not bad for 1.6

  8. #8
    ragav123 is offline Member
    Join Date
    May 2010
    Posts
    4
    Rep Power
    0

    Default

    :). Okay.. I will go through the doc. Thanks for your immediate and prompt response.

  9. #9
    toadaly is offline Senior Member
    Join Date
    Jan 2009
    Posts
    671
    Rep Power
    6

    Default

    Usually, JVM crashes are caused by 1 of two issues:

    - The installed jar/class files were changed while the jvm was running. This happens a lot in development environments where new installs are getting pushed out, or you recompile while you're running

    - You are using JNI and your code causes a seg fault.

  10. #10
    Tolls is offline Moderator
    Join Date
    Apr 2009
    Posts
    12,224
    Rep Power
    20

    Default

    And this is a seg fault, since that's what a SIGSEGV means doesn't it?
    And I took a guess at 0xb implying a null pointer.

  11. #11
    toadaly is offline Senior Member
    Join Date
    Jan 2009
    Posts
    671
    Rep Power
    6

    Default

    Yah, segfault = segmentation violation - an attempt to access memory outside the process space, which is the same as SIGSEGV.

  12. #12
    chitra_12 is offline Member
    Join Date
    Nov 2014
    Posts
    1
    Rep Power
    0

    Default Re: JVM crash in Linux

    Quote Originally Posted by toadaly View Post
    Yah, segfault = segmentation violation - an attempt to access memory outside the process space, which is the same as SIGSEGV.

    Hi ,

    I m also facing the issue.Can you please let me know the solution for the issue.


    Please find the attached log files for reference.

  13. #13
    gimbal2 is offline Just a guy
    Join Date
    Jun 2013
    Location
    Netherlands
    Posts
    4,354
    Rep Power
    6

    Default Re: JVM crash in Linux

    I can hardly believe you have the same issue, as then you would be running the same application on an ancient version of Java 6 on a very old Linux kernel.

    No you may have the same result, but what leads to that result is 100% different. Create a new thread and provide as much specifics about your environment as you can.
    "Syntactic sugar causes cancer of the semicolon." -- Alan Perlis

Similar Threads

  1. Linux Shell
    By rp181 in forum Advanced Java
    Replies: 2
    Last Post: 01-30-2010, 05:51 AM
  2. Replies: 2
    Last Post: 08-04-2009, 01:35 AM
  3. Replies: 6
    Last Post: 04-08-2009, 05:05 AM
  4. Help Making a program not crash
    By Lifeis2evil in forum New To Java
    Replies: 2
    Last Post: 12-10-2008, 04:10 AM
  5. Replies: 0
    Last Post: 01-28-2008, 08:02 AM

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •