paul williams
Assigned
Reported
Comments
@unknown,
@unknown
I can't claim that this solved the bug, but the steps I took that solved it for me were:
Start Minecraft Launcher
Select "Launch options" tab
Select your world
Enable Java executable (should say something like "C:\Program Files (x86)\Minecraft\runtime\jre-x64\bin\javaw.exe", previously "<Use bundled Java runtime>", unless you have already overridden the Java executable before, in which case disable the Java executable, so that it reverts to bundled Java runtime)
Click on SAVE
Optionally check the world options again (you should find that the Java executable has reverted to "<Use bundled Java runtime>")
Select "News" tab
PLAY your world
Anyone please post a message saying whether this makes any difference, or not.
>OK. Using the bundled Java runtime and am able to connect to 1.12.2 without timeouts
Hi again. I haven't had this problem since last time (28/Apr/2018) ... until now, with 1.14.2 pre-release 4. Same problem on two computers "Internal Exception: java.io.IOException: An existing connection was forcibly closed by the remote host." This happens after about 20 seconds of connection, while stuff loads.
Finally, I tried disabling the bundled Java executable and using the one configured (i.e. C:\Program Files (x86)\Minecraft\runtime\jre-x64\bin\javaw.exe). I found that after saving the change and reopening the launch options to double-check that the change persisted that it had reverted to the bundled Java executable. Of course, this makes sense as the one configured is the bundled one.
But this allowed me to login and not get disconnected due to timeout. In other words, changing the default Java executable to the explicit URL of the default Java executable fixed the problem. I haven't used a non-default Java since I had the problem with 1.12.2, but forcing it to re-save the option to use the bundled version appears to make the timeout issue go away.
I note that this bug is still un-resolved, although the other issue links are all resolved, probably because they were not the same problem. Obviously there are many people reporting the same symptoms with recent versions, since this bug was created in 2013.
Could it be that the default bundled Java option is not the one that is configured (i.e. C:\Program Files (x86)\Minecraft\runtime\jre-x64\bin\javaw.exe)?
OK. Using the bundled Java runtime and am able to connect to 1.12.2 without timeouts, at least so far. I'm sure I tried this before, but now it's working. The latest Java 8 is still an option, If it starts failing again.
I would be interested to hear if other people have success with this, or are still getting the "forcibly closed by the remote host" error.
Same issue when upgraded to 1.12.2. Problem disappears if revert to 1.12.1.
The "forcibly closed by the remote host" popup is displayed 30 seconds after connecting to server, this period beginning after "Loading terrain" finishes.
I tried:
connecting with a second computer, with no success
changing to old Java launcher, as suggested by @Sam P, with no success
overriding the Java version, instead of the bundled version, but that made no success
disable NAT acceleration, as suggested by @demonishh, with no success
checking server log (only shows "lost connection: Disconnected")
checking client log, including info and debug messages (only shows "Connecting" then "Loaded 382 advancements" after 20 seconds, at the same time that “Loading Textures” finishes being displayed and the 30 second period begins)
revert to previous version (1.12.1), with success
It feels like a server-initiated "keep alive" packet is not responded to by my client, within the 30 second period described in "Keep Alive (clientbound)" section at http://wiki.vg/Protocol#Keep_Alive_.28clientbound.29.
I'll be interested to see if the problem still exists for version 1.12.3.
I'll also take the computer to work, next week, to see if the different environment makes any difference.
Are there any other things that can be checked?
PS, another user on the same server had no connection problems. 😞
yes, shift click with multiple stacks will cause disconnect. for example, if i have two stacks of cobblestone and craft the furnace recipe it will disconnect me but if i have one and a bit stacks (e.g 64 and 56 cobblestone) it successfully makes the furnaces (15 in this case). it's a useful technique to process gold nuggets, etc. where your inventory is full of the raw materials. 🙂
@unknown,
You're looking here at a duplicate of MC-34947, which has been closed and reopened more times than this task. That's the task that currently represents this problem.