Christopher Webb

Update: Now trying to launch the server in order to play, and it is still >80% hang as previously described. I'm not sure if running an instance of the Java Edition in addition to the server on the same machine is a factor.

I've tried the two snapshots this week (18w08a and 18w08b), and both of them appear to be working with my original parameters. I have not had a chance to jump into the game and try things, but the server launches successfully.

I see the same issue: First time I connect to my server (running on the same machine, using localhost, if that matters), I get this exception. If I try again immediately, I can connect successfully.

If I stop the server and start it again later, the same exception occurs on first attempt to connect.

Edit: This is on 17w13b. Did not see with 17w06a. I don't remember it with 17w13a, either.

I disagree: I was not asking for Mojang to assist me in this issue. This was an attempt at a courtesy notice that Java has updated, and it appears to have introduced side-effects with the minecraft server 11.2 jar. Per Oracle's policy, when crashes are uncovered in a Java app after updating the Java version, an issue should be raised with the app creators, so I attempted to do so. However, apparently that was a mistake on my part. My apology.

@violine1101 – Ohhhh. I've never encountered that before. Those blocks must be right on the edge of the radius. I just reviewed the description on the wiki for that parameter. It looks like it's happening now because one of us is OP, and the other isn't.

Sorry for the misunderstanding. I'll adjust the parameters appropriately and/or de-OP myself. I guess this can be closed as "not a bug".

Client player log for the player in question.

The client log in question shows several errors around the time the player tried to interact with the door. I'll attach the log, FWIW - the interaction with the "problem" door is around 09:15:xx in the log.

[09:15:26] [Client thread/ERROR]: Null returned as 'hitResult', this shouldn't happen!

Other player is not OP. They are able to interact with other things in the region (double doors, crops, chests, etc). Maybe I'm using the term "worldspawn" incorrectly - I mean the region of the world where the players initially spawn. The world is configured as a Survival world, and both players are in Survival mode. All of the construction has been done in survival mode. I don't understand why the other player would need to be OP to interact with doors on this world - I haven't seen this on previous server worlds we've run in-house, going back to 1.7.10.

Some elements of the construction I've done near that chunk of the world (specifically, some single doors) do not work for the other player, but other elements do work, including pressure plates adjacent to the single doors that are not working for the other player. If I remove one of the problem doors, the other player is unable to replace it with a door from his own inventory. I can replace the door, and it works normally for me, but it still does not work for him if he clicks on it.

Also seeing the same problem on local-host server 16w39a and client 16w39a: Place charcoal in the furnace, the client crashes (server does not). Server log includes "Internal Exception: java.io.IOException: An existing connection was forcibly closed by the remote host" at time when the client crashes.