Upgrading JBossWeb causes the JVM to crash due to JBoss Native incompatibility

Solution Verified - Updated -

Issue

  • We put the patch JBPAPP-3434 in production, and JBoss refused to start.
  • The JVM crashing with the following error in the fatal error log:
    #
# A fatal error has been detected by the Java Runtime Environment:
#
#  EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x3d7f8a39, pid=1704, tid=3484
#
# JRE version: 6.0_18-b07
# Java VM: Java HotSpot(TM) Server VM (16.0-b13 mixed mode windows-x86 )
# Problematic frame:
# C  [libapr-1.dll+0x8a39]
#
# 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 (0x33d70800):  JavaThread "main" [_thread_in_native, id=3484, stack(0x34270000,0x342c0000)]

siginfo: ExceptionCode=0xc0000005, reading address 0x00000018

Environment

  • JBoss Enterprise Application Platform (EAP) 5.0 with patch JBPAPP-3434 applied.

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

New to Red Hat?

Learn more about Red Hat subscriptions

Close

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