Hide Forgot
Description of problem: Opening SSL/TLS connection randomly causes JVM crash. Version-Release number of selected component: java-1.8.0-openjdk-devel-1.8.0.111-4.b16.fc26 Additional info: reporter: libreport-2.9.0 backtrace_rating: 4 cmdline: /usr/lib/jvm/java/bin/java -agentpath:/usr/lib/abrt-java-connector/libabrt-java-connector.so=abrt=on -Xshare:auto -XX:+UseRTMLocking -XX:+UseRTMDeopt -XX:+UseLargePagesInMetaspace -Doracle.jdbc.maxCachedBufferSize=0 -Dnet.sf.ehcache.skipUpdateCheck=true -noverify -Djava.security.egd=file:///dev/./urandom -XX:AutoBoxCacheMax=1000 -Dmaven.artifact.threads=10 -classpath /usr/share/java/plexus-classworlds.jar -Dclassworlds.conf=/usr/share/maven/bin/m2.conf -Dmaven.home=/usr/share/maven -Dmaven.multiModuleProjectDirectory=/home/mtiihone/elisa/ya/chameleon-rest -Dlibrary.jansi.path=/usr/share/maven/lib org.codehaus.plexus.classworlds.launcher.Launcher clean install crash_function: os::abort(bool) executable: /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.111-4.b16.fc26.x86_64/bin/java global_pid: 9852 kernel: 4.10.0-0.rc2.git4.2.fc26.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (3 frames) #2 os::abort(bool) at /usr/src/debug/java-1.8.0-openjdk-1.8.0.111-4.b16.fc26.x86_64/openjdk/hotspot/src/os/linux/vm/os_linux.cpp:1500 #3 VMError::report_and_die() at /usr/src/debug/java-1.8.0-openjdk-1.8.0.111-4.b16.fc26.x86_64/openjdk/hotspot/src/share/vm/utilities/vmError.cpp:1060 #4 JVM_handle_linux_signal(int, siginfo_t*, void*, int) at /usr/src/debug/java-1.8.0-openjdk-1.8.0.111-4.b16.fc26.x86_64/openjdk/hotspot/src/os_cpu/linux_x86/vm/os_linux_x86.cpp:556 Potential duplicate: bug 1406913
Created attachment 1238745 [details] File: backtrace
Created attachment 1238746 [details] File: cgroup
Created attachment 1238747 [details] File: core_backtrace
Created attachment 1238748 [details] File: dso_list
Created attachment 1238749 [details] File: environ
Created attachment 1238750 [details] File: limits
Created attachment 1238751 [details] File: maps
Created attachment 1238752 [details] File: mountinfo
Created attachment 1238753 [details] File: namespaces
Created attachment 1238754 [details] File: open_fds
Created attachment 1238755 [details] File: proc_pid_status
Created attachment 1238756 [details] File: var_log_messages
I think this is same issue as reported in #1411116.
This bug appears to have been reported against 'rawhide' during the Fedora 26 development cycle. Changing version to '26'.
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '26'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 26 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.