Forum Stats

  • 3,838,711 Users
  • 2,262,395 Discussions
  • 7,900,739 Comments

Discussions

JVM (java 1.6.0_20) crashed with SIGBUS error in the hot spot core dump log

865505
865505 Member Posts: 3
edited Jun 3, 2011 10:36AM in Java Native Interface (JNI)
We have a service that uploads a csv(comma separated data file) file from the remote server to local location and then process each record in that file one afer the other.

Recently we have observed a crash in JVM while uploading a list with problem frame ponted to libzip.so file.
It was clearly communicated that the crash is out side the JVM in native code.
This upload can be done using different protocols(FTP, SCP. SFTP...etc). We are using third party API pakages for this upload activity.

Please inform if anything you can add to this mail...

Thanks in advance,
-RAM-
Tagged:

Answers

  • 865505
    865505 Member Posts: 3
    Here is the hot spot error log.


    [[email protected] ~]$ cat /home/ebiz40/hs_err_pid30864.log
    #
    # An unexpected error has been detected by Java Runtime Environment:
    #
    # SIGBUS (0x7) at pc=0x00002aaaab03f031, pid=30864, tid=1119217984
    #
    # Java VM: Java HotSpot(TM) 64-Bit Server VM (11.0-b16 mixed mode linux-amd64)
    # Problematic frame:
    # C [libzip.so+0xb031]
    #
    # If you would like to submit a bug report, please visit:
    # http://java.sun.com/webapps/bugreport/crash.jsp
    # The crash happened outside the Java Virtual Machine in native code.
    # See problematic frame for where to report the bug.
    #

    --------------- T H R E A D ---------------

    Current thread (0x00002aaac4096c00): JavaThread "TBSU-ImportProcess" [_thread_in_native, id=31253, stack(0x0000000042a5e000,0x0000000042b5f000)]

    siginfo:si_signo=SIGBUS: si_errno=0, si_code=2 (BUS_ADRERR), si_addr=0x00002aaac2224af1

    Registers:
    RAX=0x0000000000000000, RBX=0x000000005470d9e8, RCX=0x0000000000000070, RDX=0x00002aaac8b62b30
    RSP=0x0000000042b5be80, RBP=0x00002aaac2224ad4, RSI=0x00000035291529e0, RDI=0x00002aaac80001e8
    R8 =0x0000000000000000, R9 =0x0000000000000000, R10=0x00002aae378c5418, R11=0x00002aae378c8e88
    R12=0x00002aaac8b62af0, R13=0x000000005470b460, R14=0x0000000042b5bf10, R15=0x0000000000000029
    RIP=0x00002aaaab03f031, EFL=0x0000000000010206, CSGSFS=0x0000000000000033, ERR=0x0000000000000004
    TRAPNO=0x000000000000000e
  • jschellSomeoneStoleMyAlias
    jschellSomeoneStoleMyAlias Member Posts: 24,877 Gold Badge
    Does your code or the third party code use native code (JNI)?
  • 866439
    866439 Member Posts: 2
    I am also facing the exact issue. Did you find any solution for this?
  • 802316
    802316 Member Posts: 532
    I had a similar problem with Java 6 update 18 when reading a truncated ZIP/JAR file.

    Since using Java 6 update 23 and 25 I haven't had this problem.
  • 866439
    866439 Member Posts: 2
    We have 1.5.0_22-b03 on testing environment and it is working fine. But same 1.5.0_22-b03 in production environment is having the issue.
This discussion has been closed.