[
https://issues.jboss.org/browse/JBAS-8717?page=com.atlassian.jira.plugin....
]
Joel Rabinovitch commented on JBAS-8717:
----------------------------------------
Hi,
I can confirm that the same problem occurs with JBoss 6.1 with Redhat Enterprise 6.0.
There appears to be a conflict with mod_jk.so and the JBoss Native libraries.
If you install the JBoss Native files in the bin/native directory, you get the following
core dump:
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007f27bbbdb639, pid=5768, tid=139808600811264
#
# JRE version: 6.0_27-b07
# Java VM: Java HotSpot(TM) 64-Bit Server VM (20.2-b06 mixed mode linux-amd64 co
mpressed oops)
# Problematic frame:
# C [libapr-1.so.0+0x1e639] signed char+0x49
#
# An error report file with more information is saved as:
# /apps/jboss-6.1.0.Final-jdk-1.6.0/bin/hs_err_pid5768.log
#
# 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.
#
Using JDK 1.6.0_23 produces a similar message.
I tried using JBoss Native 2.09 and 2.10 and it does not work. I even tried recompiling
the JBoss Native source code, but it does not resolve the problem.
If you remove the files, things work correctly.
Is there any chance of this being fixed in the 6.x series?
Thanks,
Joel
JBoss 6 RC1 crash when using MOD_JK
-----------------------------------
Key: JBAS-8717
URL:
https://issues.jboss.org/browse/JBAS-8717
Project: Legacy JBoss Application Server 6
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 6.0.0.CR1
Environment: Linux CEntOS 5.5, JDK 1.6.0_23-b05
Reporter: Kleber Rocha
Fix For: No Release
JBoss work fine, but when I configure Apache with mod_jk and I start a connection, JBoss
crash and create a file hs_err_pidXXXX.log, with this information:
# JRE version: 6.0_23-b05
# Java VM: Java HotSpot(TM) 64-Bit Server VM (19.0-b09 mixed mode linux-amd64 compressed
oops)
# Problematic frame:
# C [libapr-1.so.0+0x1b58f] apr_pollset_add+0x8f
This don´t happen with M5.
Exist any workaround for this?
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira