-
-
Notifications
You must be signed in to change notification settings - Fork 3.4k
Server sometimes can stuck on "Reloading ResourceManager" #6020
Copy link
Copy link
Closed
Labels
status: acceptedDisputed bug is accepted as valid or Feature accepted as desired to be added.Disputed bug is accepted as valid or Feature accepted as desired to be added.type: bugSomething doesn't work as it was intended to.Something doesn't work as it was intended to.version: 1.17Game version 1.17Game version 1.17version: 1.18Game version 1.18Game version 1.18
Metadata
Metadata
Assignees
Labels
status: acceptedDisputed bug is accepted as valid or Feature accepted as desired to be added.Disputed bug is accepted as valid or Feature accepted as desired to be added.type: bugSomething doesn't work as it was intended to.Something doesn't work as it was intended to.version: 1.17Game version 1.17Game version 1.17version: 1.18Game version 1.18Game version 1.18
Type
Fields
Give feedbackNo fields configured for Bug.
Projects
Status
Done
Expected behavior
The server is starting.
Observed/Actual behavior
The server is not starting.
Steps/models to reproduce
This is not the first time I have encountered this. I do not know how to reproduce this. This happens randomly, possibly depending on the phase of the moon :/
It looks like the server thread is waiting for something or another important thread is stuck on something, but I do not know how and where to look at the stack trace. Right now the server is in this state and still running, so if you can tell me which program can be used to see what its process is doing, I will send you the necessary information to fix this problem.
This is always looks like this:

And that's all. Time in now 13:20, CPU load in the task manager is ~1%, the server took up 2 MiB of RAM and just does nothing until it is restarted..
Listening for transport dt_socket at address: 1023on the last line: I tried to connect to server via Eclipse Debug, but later disconnected because it did not give me any info :cPlugin list
null
Paper version
I encountered this problem back on versions 1.15 and 1.14, but it happened rarely and I did not think that it would happen again in new versions. Maybe this has already been fixed in 1.17, but I think not.
Agreements
Other
No response