Bug 2039174

Summary: The problem started 2 days ago, our server is shutting down 8 times a day
Product: Red Hat Enterprise Linux 8 Reporter: Epolision Han <celalegent>
Component: java-1.8.0-openjdkAssignee: Andrew John Hughes <ahughes>
Status: CLOSED WONTFIX QA Contact: OpenJDK QA <java-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 8.0CC: jvanek
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-07-11 07:28:16 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Crash Report Logs none

Description Epolision Han 2022-01-11 07:01:34 UTC
Created attachment 1850025 [details]
Crash Report Logs

Description of problem:
Minecraft server shuts down suddenly without any error in log files


Version-Release number of selected component (if applicable):

Spigot 1.8, Centos 8.0

How reproducible:

I'm having this crash report 5, 6 more in a day

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 jiri vanek 2022-01-11 12:40:23 UTC
Hello!
there were an updates of rhel.8, and osme had java included. What rhel8 are you on?  8.1?  8.2?  8.3?  8.4?  8.5?
The updates were
8.1 Tue 2021-12-21
8.2 Tue 2022-01-11 	
8.3 dead
8.4 Tue 2021-12-14
8.5 Tue 2021-12-21

TBH, I'm not sure which contaied jdk8 and which not.
Do you have details of your last dnf trasnactions - but generally spoken  - except 8.2, which went out today, all were longer then 2days ago, but yo could update later.

note for other readers, there is an stack trace in attachment.

@Epolision Han, is the header of the stack trace you attached always (nearly) same?

Comment 3 RHEL Program Management 2023-07-11 07:28:16 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.