JVM crashes when HDScanner thread was active

Solution Unverified - Updated -

Issue

  • While redeployment of an application jvm crashes and the hs_err file shows that HDScanner was the current thread when crash happened.
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00007f1c0901bbe0, pid=20361, tid=139756310783744
#
# JRE version: 6.0_24-b24
# Java VM: OpenJDK 64-Bit Server VM (20.0-b12 mixed mode linux-amd64 compressed oops)
# Derivative: IcedTea6 1.11.9
# Distribution: Red Hat Enterprise Linux Server release 6.4 (Santiago), package rhel-1.57.1.11.9.el6_4-x86_64
# Problematic frame:
# j  javax.management.JMRuntimeException.<init>(Ljava/lang/String;)V+2
#
# If you would like to submit a bug report, please include
# instructions how to reproduce the bug and visit:
#   http://icedtea.classpath.org/bugzilla
#
---------------  T H R E A D  ---------------

Current thread (0x00007f1bb1da1000):  JavaThread "HDScanner" [_thread_in_Java, id=20488, stack(0x00007f1b8d3a6000,0x00007f1b8d427000)]

siginfo:si_signo=SIGSEGV: si_errno=0, si_code=2 (SEGV_ACCERR), si_addr=0x000000009f129bd8

Environment

  • JBoss Enterprise Application Platform (EAP)
    • 5.x.x
  • OpenJDK Java
    • 1.6_24

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.