Bug 208553 - java/openjdk8 always crash with wildfly-10.0.0
Summary: java/openjdk8 always crash with wildfly-10.0.0
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: freebsd-java (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-04-05 14:50 UTC by huanghwh
Modified: 2016-06-18 19:50 UTC (History)
3 users (show)

See Also:


Attachments
hs_err.log (54.44 KB, text/x-log)
2016-04-05 14:50 UTC, huanghwh
no flags Details
hs_err_pid50422.log (93.27 KB, text/x-log)
2016-04-05 14:51 UTC, huanghwh
no flags Details
hs_err_pid51043.log (94.48 KB, text/x-log)
2016-04-05 14:52 UTC, huanghwh
no flags Details
hs_err_pid19610.log (509.93 KB, text/x-log)
2016-05-03 00:25 UTC, huanghwh
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description huanghwh 2016-04-05 14:50:02 UTC
Created attachment 169007 [details]
hs_err.log

This problem can easily trigger with my program under wildfly-10.0.0

root@zb1:/usr/local/wildfly-10.0.0 # uname -a
FreeBSD zb1.jopens.cn 10.3-RELEASE FreeBSD 10.3-RELEASE #0 r297264: Fri Mar 25 02:10:02 UTC 2016     root@releng1.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC  amd64
root@zb1:/usr/local/wildfly-10.0.0 # java -version
openjdk version "1.8.0_77"
OpenJDK Runtime Environment (build 1.8.0_77-b03)
OpenJDK 64-Bit Server VM (build 25.77-b03, mixed mode)
Comment 1 huanghwh 2016-04-05 14:51:44 UTC
Created attachment 169008 [details]
hs_err_pid50422.log
Comment 2 huanghwh 2016-04-05 14:52:27 UTC
Created attachment 169009 [details]
hs_err_pid51043.log
Comment 3 yerenkow 2016-04-10 17:39:59 UTC
Is there any hints on to what your application doing, or maybe you cand strip out to smallest code possible?

Not sure this could be related to wildfly itself, but who knows, would be interesting to look into.
Comment 4 Jung-uk Kim freebsd_committer freebsd_triage 2016-04-14 22:02:19 UTC
If you don't want to see the annoyance, please turn off DEBUGFAST option.
Comment 5 huanghwh 2016-04-26 00:37:18 UTC
My application just get seismic waveform from http, about 9000 channels, 500KB/s.
and save to disk, one file per channel.

If run java without DEBUG/FAST, java often crash in these 4 threads:

0x00000008034f9000 VMThread [stack: 0x00007fffdc7c7000,0x00007fffdc8c7000] [id=101580]

0x000000080344a800 JavaThread "C2 CompilerThread0" daemon [_thread_blocked, id=100888, stack(0x00007fffdc2c2000,0x00007fffdc3c2000)]

0x00000008034e9800 (exited) GCTaskThread [stack: 0x00007fffdeaea000,0x00007fffdebea000] [id=100404]

0x00000008034f9800 WatcherThread [stack: 0x00007fffdb2b2000,0x00007fffdb3b2000] [id=101602]

but not always.
Comment 6 huanghwh 2016-05-03 00:25:49 UTC
Created attachment 169899 [details]
hs_err_pid19610.log

New crash:
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x0000000800835a4d, pid=19610, tid=102572
#
# JRE version: OpenJDK Runtime Environment (8.0_77-b03) (build 1.8.0_77-b03)
# Java VM: OpenJDK 64-Bit Server VM (25.77-b03 mixed mode bsd-amd64 )
# Problematic frame:
# C  [libz.so.6+0xaa4d]  _tr_flush_block+0xb1d
#
# Core dump written. Default location: /usr/local/wildfly-10.0.0/java.core
#
# If you would like to submit a bug report, please visit:
#   http://bugreport.java.com/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 (0x00000014fc820800):  JavaThread "sssPort_aws" daemon [_thread_in_native, id=102572, stack(0x00007fffbe2e5000,0x00007fffbe3e5000)]

siginfo: si_signo: 11 (SIGSEGV), si_code: 1 (SEGV_MAPERR), si_addr: 0x0000000000000000
Comment 7 openjdk 2016-05-03 14:37:37 UTC
We're there any upgrades you did, that caused it to start crashing?
Comment 8 huanghwh 2016-06-11 22:33:29 UTC
After add patch from Bug 210191, I do NOT get wildfly-10.0.0 crash until now.
Comment 9 huanghwh 2016-06-18 19:50:06 UTC
I think openjdk8-8.92.14_3 should fixed my problem.