Jump to content

Recommended Posts

Posted

Trying to debug some of my code, I was in the debugging perspective after hitting a breakpoint which paused the server thread.

 

After about a minute, the dedicated server terminal window closed with the following message:

[22:24:14] [Server Watchdog/FATAL]: A single server tick took 60.12 seconds (should be max 0.05)
[22:24:14] [Server Watchdog/FATAL]: Considering it to be crashed, server will forcibly shutdown.

 

Great, thanks guys. :|

 

And the crash log it generated:

 

  Reveal hidden contents

Apparently I'm a complete and utter jerk and come to this forum just like to make fun of people, be confrontational, and make your personal life miserable.  If you think this is the case, JUST REPORT ME.  Otherwise you're just going to get reported when you reply to my posts and point it out, because odds are, I was trying to be nice.

 

Exception: If you do not understand Java, I WILL NOT HELP YOU and your thread will get locked.

 

DO NOT PM ME WITH PROBLEMS. No help will be given.

  • 11 months later...
Posted

This is a pretty old post but I'm responding since it might be useful for others. Also I'm not sure what your question is, but I'm assuming you want to know how to handle this.

 

In the server.properties file in the run directory of your server there's a line which controls the maximum amount of time a tick can take before the server shuts down. The line is max-tick-time (near the top of the file at the time of writing). Increase it's value to something more reasonable for debugging.

Guest
This topic is now closed to further replies.

Announcements



×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.