Yup this error is in 1.8, I built a standard skeleton XP Farm and if I get more than 40-50 mobs waiting, I get kicked out with that stupid error, but same build on a test server in 1.7.10 and I have no problems, I actually I'm running a test in 1.7.10 at this exact moment, I have 161 mobs waiting and so far no problems except low fps but I don't consider this a real problem, it is normal I would say for this amount of mobs), there is something in 1.8 that does this, I have it also loaded in a 14w32 snapshot and got the same problem but if I load it in a 14w21b (the snapshot I've stopped playing at to play a modded 1.7.10 serie, I don't see this problem happening, so they screwed up something really badly in the latest ones regarding entities.
The Meaning of Life, the Universe, and Everything.
Join Date:
1/16/2012
Posts:
51
Minecraft:
AzazelEldritch
Member Details
The kick out is from the "Watch dog" if the server lags to far behind it will crash the server... But the issue is why 1 server tick is taking 60 seconds. You can disable the watchdog but that will not stop the lag.
The kick out is from the "Watch dog" if the server lags to far behind it will crash the server... But the issue is why 1 server tick is taking 60 seconds. You can disable the watchdog but that will not stop the lag.
How do you disable that crap out of my server, not sure why it keeps kicking me out, I almost forgot that the game regularly lag me out for up to 20-30 seconds, it happens randomly, sometimes I don't get it for 3hrs then suddenly I get it 3 to 5 times in 15-20 minutes of playing, I've never ever experienced this on my 1.7.10 server, so they screwed up something with the 1.8 server somehow. Just to be clear, on both the normal server at my brother house and on my test server, the game is on a SSD drive and works #1.
The Meaning of Life, the Universe, and Everything.
Join Date:
1/16/2012
Posts:
51
Minecraft:
AzazelEldritch
Member Details
to disable it go to your server properties it should say "max-tick-time=6000" change that to -1 to disable it. Although this will not stop the server from lagging. it will only keep it from crashing.
Checked things up, I don't have this on my 1.7.10 server and also not on my previous snapshots servers, maybe this is why I've never seen tha problem before
The Meaning of Life, the Universe, and Everything.
Join Date:
1/16/2012
Posts:
51
Minecraft:
AzazelEldritch
Member Details
Yeah its a new "Feature" with 1.8 that "stops the server properly" if it lags behind to far. its designed to where if the game is lagging it will stop the server in a safe way. but the way it works is that it "Assumes" that the server is going to crash. More annoying than a good thing in my opinion.
Yeah its a new "Feature" with 1.8 that "stops the server properly" if it lags behind to far. its designed to where if the game is lagging it will stop the server in a safe way. but the way it works is that it "Assumes" that the server is going to crash. More annoying than a good thing in my opinion.
I don't really care if it crash, I can restart it, the world is backed up every 4hrs, thanks to Cobian Backup for this.
Now I see the server complaining about tick time, even if we're not online, some ticks take more than 2345ms which I've never ever seen that error on my 1.7.10 or 14w21b server, there must be something else they need to fix. Also didn't stop the lag, but I think they will fix that part in a future patch somehow.
The Meaning of Life, the Universe, and Everything.
Join Date:
1/16/2012
Posts:
51
Minecraft:
AzazelEldritch
Member Details
I am starting to believe this issue is just a connectivity issue. What i do not understand is why it is only an issue with 1.8 and not anything prior. On my 1.7.10 server i have a player log on and everything is fine. I switch to the 1.8 server and the same person logs on and then instantly disconnects or creates copies of them self trying to connect. Also I have no issues with connection since I am hosting my own server from my own computer. But if I try to connect to another player's server i get a different exception. Not sure if they are related.
I am starting to believe this issue is just a connectivity issue. What i do not understand is why it is only an issue with 1.8 and not anything prior. On my 1.7.10 server i have a player log on and everything is fine. I switch to the 1.8 server and the same person logs on and then instantly disconnects or creates copies of them self trying to connect. Also I have no issues with connection since I am hosting my own server from my own computer. But if I try to connect to another player's server i get a different exception. Not sure if they are related.
I've read that they switched the network protocol they use in the latest Minecraft 1.8 version and there was a debate between some pro dev that told them it wasn't a good idea and that it would cause a lot of problems, but still they did it, not sure what is it about exactly cause I know nothing about java programming but some people said that Mojang did a really bad choice with the way they changed the network protocol of Minecraft, If what I've read is right, the network protocol they use now is made for home network and works really bad if it has to go through the Internet because it doesn't tolerate errors and lag very well.
I am getting the same error every few minutes, it seems I haven't found anyone yet that has a true solution. I have my own server (1.5GB through Exodus hosting) and customer support basically said, your server is fine, we don't know what the error is, try running bukkit - but there's no 1.8 release for bukkit. .. has anyone had any luck resolving the issue? This does not happen in a single player world; only on the server. It seems to drive the memory usage to 100% (WAY more than 2 players should be using for a 1.5 GB server!), but Exodus doesn't have an answer for that either.
Rollback Post to RevisionRollBack
Find us on Youtube, Facebook, Twitter, Tumblr, Google+, and Instagram @NotQuiteNerds
I am getting the same error every few minutes, it seems I haven't found anyone yet that has a true solution. I have my own server (1.5GB through Exodus hosting) and customer support basically said, your server is fine, we don't know what the error is, try running bukkit - but there's no 1.8 release for bukkit. .. has anyone had any luck resolving the issue? This does not happen in a single player world; only on the server. It seems to drive the memory usage to 100% (WAY more than 2 players should be using for a 1.5 GB server!), but Exodus doesn't have an answer for that either.
I have read a Thread about this issue being due to water but I have been in a super flat world with no water and had this same issue when i was helping a player build something on his personal server. So i do not think this is the case. Something with the connection programming is the issue in my opinion.
The Meaning of Life, the Universe, and Everything.
Join Date:
1/16/2012
Posts:
51
Minecraft:
AzazelEldritch
Member Details
I believe i may have found a FIX Please test this theory and tell me your results. Download the 64 bit version of java and make sure the system path for java goes to the 64 bit version. Also allocate at least 2 gigs of ram to the server.
Is there a specific way to make sure the server start with java 64 bits, I was sure that giving the instructions to allocate 2GB in the server.bat was enough but now I have a doubt, I know that normally 32 bits version of java wouldn't allocate more than 1GB, but maybe the server doesn't care at all.
For the client side, its obvious when we hit F3 that my client use 64bits and is allowed 2GB of memory.
I tend to only get this error if i have no internet connection.
How do you disable that crap out of my server, not sure why it keeps kicking me out, I almost forgot that the game regularly lag me out for up to 20-30 seconds, it happens randomly, sometimes I don't get it for 3hrs then suddenly I get it 3 to 5 times in 15-20 minutes of playing, I've never ever experienced this on my 1.7.10 server, so they screwed up something with the 1.8 server somehow. Just to be clear, on both the normal server at my brother house and on my test server, the game is on a SSD drive and works #1.
I don't really care if it crash, I can restart it, the world is backed up every 4hrs, thanks to Cobian Backup for this.
Now I see the server complaining about tick time, even if we're not online, some ticks take more than 2345ms which I've never ever seen that error on my 1.7.10 or 14w21b server, there must be something else they need to fix. Also didn't stop the lag, but I think they will fix that part in a future patch somehow.
I've read that they switched the network protocol they use in the latest Minecraft 1.8 version and there was a debate between some pro dev that told them it wasn't a good idea and that it would cause a lot of problems, but still they did it, not sure what is it about exactly cause I know nothing about java programming but some people said that Mojang did a really bad choice with the way they changed the network protocol of Minecraft, If what I've read is right, the network protocol they use now is made for home network and works really bad if it has to go through the Internet because it doesn't tolerate errors and lag very well.
I have read a Thread about this issue being due to water but I have been in a super flat world with no water and had this same issue when i was helping a player build something on his personal server. So i do not think this is the case. Something with the connection programming is the issue in my opinion.
For the client side, its obvious when we hit F3 that my client use 64bits and is allowed 2GB of memory.
java -Xms2G -Xmx3G -XX:+UseG1GC -XX:MaxGCPauseMillis=25 -server -jar server.jar nogui
pause
http://minecraft.gamepedia.com/Tutorials/Setting_up_a_server
Go down to the section "Permanently modifying the system path"
This should make 64 bit Java default.