Kyle Lane

Here's a question, could Max Tick Time have any affect on this situation? I remember changing that in my server properties a while back, but looking back I didn't really understand what that setting does and can't find a good explanation online.

Can anyone elaborate?

You've helped confirm what I've discovered in the last few hours.

Even though the server computer should have more than enough ram to accommodate 2GB, the threshold of mobs that causes the error is much higher if I'm only setting the server to 1GB (causing MUCH less errors).

So thankfully, I feel like I've solved our servers issue. Hopefully that helps someone else, I haven't seen "lowering your RAM" be a solution anywhere before.

Thanks man

Ben, you have some good points, however the fact still remains that this wasn't a problem for many of us until the pre-releases of 1.8. So obviously something on their end has changed to cause an influx of this error.

I would add to your post by saying that there isn't one solution. After doing research on this error for months I've found that people get it for 1,000 different reasons so there most likely isn't a single fix. My server, for instance, gets this error when I either have too many animals, or I breed them too quickly. From that point on the server is goofed up for upwards of a week, or whenever it decides to start working again.

Edit: Something else to add. I had previously been allocating 2GB or 3GB of RAM to my server, I just reduced the RAM to 1GB and it's working. Could it be that the computer is running the server "faster" than the network can and it never catches up?