Dedicated server logs "java.io.IOException: The handle is invalid" on startup
This error should not have any side effects and can be ignored (see section "Code analysis" for an explanation).
When starting the server from the command line no error is logged, for example:
java -Xmx1024M -Xms1024M -jar server.jar
The bug
When the dedicated server is started by double clicking the .jar file it logs the following error on startup:
[09:23:17 ERROR]: Exception handling console input java.io.IOException: The handle is invalid at java.io.FileInputStream.readBytes(Native Method) ~[?:1.8.0_172] at java.io.FileInputStream.read(Unknown Source) ~[?:1.8.0_172] at java.io.BufferedInputStream.read1(Unknown Source) ~[?:1.8.0_172] at java.io.BufferedInputStream.read(Unknown Source) ~[?:1.8.0_172] at sun.nio.cs.StreamDecoder.readBytes(Unknown Source) ~[?:1.8.0_172] at sun.nio.cs.StreamDecoder.implRead(Unknown Source) ~[?:1.8.0_172] at sun.nio.cs.StreamDecoder.read(Unknown Source) ~[?:1.8.0_172] at java.io.InputStreamReader.read(Unknown Source) ~[?:1.8.0_172] at java.io.BufferedReader.fill(Unknown Source) ~[?:1.8.0_172] at java.io.BufferedReader.readLine(Unknown Source) ~[?:1.8.0_172] at java.io.BufferedReader.readLine(Unknown Source) ~[?:1.8.0_172] at sn$2.run(SourceFile:107) [server.jar:?]
Code analysis
It seems that the reason for this is that the server can process commands provided from the command prompt (System.in) and independently from the JTextField. In case you do not start the server using the command prompt it still tries to read the input from it which is not possible. It appears that there is no way to prevent this because apparently System.in is not null by default and you cannot test if the readers can read without calling the reading methods and catching exceptions (which is the way it currently behaves).
As suggested in this StackOverflow answer the method InputStream.available() could be used at the start to detect if System.in is usable. If the .jar is not started from command line, then this method throws the exception as well. In this case a warning or an info message could be logged (including the exception?) and only the GUI input could be used.
Linked Issues
is duplicated by38
- Unresolved
raz
- 47
- 25
- Confirmed
Low
- Platform
- Dedicated Server
- console server
13w39a - 1.21.3
13w39a 13w39b 13w41a 13w41b 13w42b 13w43a 1.7 1.7.1 1.7.2 13w47a 13w47b 13w47c 1.7.4 14w04b 14w05b 14w06a 1.7.5 14w11b 1.7.8 1.7.9 14w21b 14w28a 14w30b 1.8.1 1.8.3 1.8.8 15w51b 1.12.1 1.12.2-pre1 1.12.2-pre2 1.12.2 17w43a 17w43b 18w01a 1.13 19w11b 19w13b 1.14.4 19w42a 1.15.2 20w18a 20w19a 1.18.1 22w03a 1.18.2 1.19 1.19.2 22w42a 1.20.1 1.20.2 24w12a 1.21 1.21.1 1.21.3
Created Issue:
server return error
server return error on start.
server return error on start.
[code] [09:23:17] [Server thread/INFO] : Starting minecraft server version 13w41b
[09:23:17] [Server console handler/ERROR] : Exception handling console input [/code]
server return error on start.
[
code][09:23:17][Server thread/INFO]: Starting minecraft server version 13w41b
[09:23:17] [Server console handler/ERROR]: Exception handling console input[/code]server return error on start.
[09:23:17] [Server thread/INFO]: Starting minecraft server version 13w41b
[09:23:17] [Server console handler/ERROR]: Exception handling console input
server return error (handler/ERROR)
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
server return error on start.
[09:23:17] [Server thread/INFO]: Starting minecraft server version 13w4
1b
[09:23:17] [Server console handler/ERROR]: Exception handling console inputserver return error on start.
[09:23:17] [Server thread/INFO]: Starting minecraft server version 13w47c
[09:23:17] [Server console handler/ERROR]: Exception handling console input
is duplicated by
is duplicated by
is duplicated by
Moderator NoteThis issue can be corrected by using java in the command line instead of javaw.exe
server return error on start.
[09:23:17] [Server thread/INFO]: Starting minecraft server version 13w47c
[09:23:17] [Server console handler/ERROR]: Exception handling console input
Moderator NoteThis issue can be corrected by using java in the command line instead of javaw.exe
server return error on start.
[09:23:17] [Server thread/INFO]: Starting minecraft server version 13w47c
[09:23:17] [Server console handler/ERROR]: Exception handling console inputModerator NoteThis issue can be corrected temporarily by using java in the command line instead of javaw.exe.
Example: java -Xmx1024M -Xms1024M -jar minecraft_server.14w03b.jar
server return error on start.
[09:23:17] [Server thread/INFO]: Starting minecraft server version 13w47c
[09:23:17] [Server console handler/ERROR]: Exception handling console input
server return error (handler/ERROR)java.io.IOException: The handle is invalid
is duplicated by
relates to
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
Moderator NoteThis issue can be corrected temporarily by using java in the command line instead of javaw.exe.
Example: java -Xmx1024M -Xms1024M -jar minecraft_server.14w03b.jar
server return error on start.
[09:23:17] [Server thread/INFO]: Starting minecraft server version 13w47c
[09:23:17] [Server console handler/ERROR]: Exception handling console input
Code analysis by Marcono1234 in this comment.
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
Dedicated server logs "java.io.IOException: The handle is invalid" on startup
Moderator NoteThis issue can be corrected temporarily by using java in the command line instead of javaw.exe.
Example: java -Xmx1024M -Xms1024M -jar minecraft_server.14w03b.jar
server return error on start.
[09:23:17] [Server thread/INFO]: Starting minecraft server version 13w47c
[09:23:17] [Server console handler/ERROR]: Exception handling console input
Code analysis by Marcono1234 in this comment.
Moderator NoteThis issue can be corrected temporarily by using java in the command line instead of javaw.exe.
Example: java -Xmx1024M -Xms1024M -jar minecraft_server.14w03b.jar
The bug
When the dedicated server is started by double clicking the .jar file it logs the following error on startup:
[03:43:55 ERROR]: Exception handling console input
java.io.IOException: Das Handle ist ungültig
at java.io.FileInputStream.readBytes(Native Method) ~[?:1.8.0_172]
at java.io.FileInputStream.read(Unknown Source) ~[?:1.8.0_172]
at java.io.BufferedInputStream.read1(Unknown Source) ~[?:1.8.0_172]
at java.io.BufferedInputStream.read(Unknown Source) ~[?:1.8.0_172]
at sun.nio.cs.StreamDecoder.readBytes(Unknown Source) ~[?:1.8.0_172]
at sun.nio.cs.StreamDecoder.implRead(Unknown Source) ~[?:1.8.0_172]
at sun.nio.cs.StreamDecoder.read(Unknown Source) ~[?:1.8.0_172]
at java.io.InputStreamReader.read(Unknown Source) ~[?:1.8.0_172]
at java.io.BufferedReader.fill(Unknown Source) ~[?:1.8.0_172]
at java.io.BufferedReader.readLine(Unknown Source) ~[?:1.8.0_172]
at java.io.BufferedReader.readLine(Unknown Source) ~[?:1.8.0_172]
at sn$2.run(SourceFile:107) [server.jar:?]
server return error on start.[09:23:17] [Server thread/INFO]: Starting minecraft server version 13w47c
[09:23:17] [Server console handler/ERROR]: Exception handling console input
Code analysis by Marcono1234 in this comment.
Moderator NoteThis issue can be corrected temporarily by using java in the command line instead of javaw.exe.
Example: java -Xmx1024M -Xms1024M -jar minecraft_server.14w03b.jar
The bug
When the dedicated server is started by double clicking the .jar file it logs the following error on startup:
[03:43:55 ERROR]: Exception handling console input
java.io.IOException: Das Handle ist ungültig
at java.io.FileInputStream.readBytes(Native Method) ~[?:1.8.0_172]
at java.io.FileInputStream.read(Unknown Source) ~[?:1.8.0_172]
at java.io.BufferedInputStream.read1(Unknown Source) ~[?:1.8.0_172]
at java.io.BufferedInputStream.read(Unknown Source) ~[?:1.8.0_172]
at sun.nio.cs.StreamDecoder.readBytes(Unknown Source) ~[?:1.8.0_172]
at sun.nio.cs.StreamDecoder.implRead(Unknown Source) ~[?:1.8.0_172]
at sun.nio.cs.StreamDecoder.read(Unknown Source) ~[?:1.8.0_172]
at java.io.InputStreamReader.read(Unknown Source) ~[?:1.8.0_172]
at java.io.BufferedReader.fill(Unknown Source) ~[?:1.8.0_172]
at java.io.BufferedReader.readLine(Unknown Source) ~[?:1.8.0_172]
at java.io.BufferedReader.readLine(Unknown Source) ~[?:1.8.0_172]
at sn$2.run(SourceFile:107) [server.jar:?]
server return error on start.[09:23:17] [Server thread/INFO]: Starting minecraft server version 13w47c
[09:23:17] [Server console handler/ERROR]: Exception handling console input
Code analysis by
Marcono1234inthis comment.Moderator NoteThis error should not have any side effects and can be ignored (see section "Code analysis" for an explanation).
When starting the server from the command line no error is logged, for example:java -Xmx1024M -Xms1024M -jar server.jarThe bug
When the dedicated server is started by double clicking the .jar file it logs the following error on startup:
1.13[09:23:17 ERROR]: Exception handling console input java.io.IOException: The handle is invalid at java.io.FileInputStream.readBytes(Native Method) ~[?:1.8.0_172] at java.io.FileInputStream.read(Unknown Source) ~[?:1.8.0_172] at java.io.BufferedInputStream.read1(Unknown Source) ~[?:1.8.0_172] at java.io.BufferedInputStream.read(Unknown Source) ~[?:1.8.0_172] at sun.nio.cs.StreamDecoder.readBytes(Unknown Source) ~[?:1.8.0_172] at sun.nio.cs.StreamDecoder.implRead(Unknown Source) ~[?:1.8.0_172] at sun.nio.cs.StreamDecoder.read(Unknown Source) ~[?:1.8.0_172] at java.io.InputStreamReader.read(Unknown Source) ~[?:1.8.0_172] at java.io.BufferedReader.fill(Unknown Source) ~[?:1.8.0_172] at java.io.BufferedReader.readLine(Unknown Source) ~[?:1.8.0_172] at java.io.BufferedReader.readLine(Unknown Source) ~[?:1.8.0_172] at sn$2.run(SourceFile:107) [server.jar:?]Code analysis
It seems that the reason for this is that the server can process commands provided from the command prompt (System.in) and independently from the JTextField. In case you do not start the server using the command prompt it still tries to read the input from it which is not possible. It appears that there is no way to prevent this because apparently System.in is not null by default and you cannot test if the readers can read without calling the reading methods and catching exceptions (which is the way it currently behaves).
Moderator NoteThis error should not have any side effects and can be ignored (see section "Code analysis" for an explanation).
When starting the server from the command line no error is logged, for example:java -Xmx1024M -Xms1024M -jar server.jarThe bug
When the dedicated server is started by double clicking the .jar file it logs the following error on startup:
1.13[09:23:17 ERROR]: Exception handling console input java.io.IOException: The handle is invalid at java.io.FileInputStream.readBytes(Native Method) ~[?:1.8.0_172] at java.io.FileInputStream.read(Unknown Source) ~[?:1.8.0_172] at java.io.BufferedInputStream.read1(Unknown Source) ~[?:1.8.0_172] at java.io.BufferedInputStream.read(Unknown Source) ~[?:1.8.0_172] at sun.nio.cs.StreamDecoder.readBytes(Unknown Source) ~[?:1.8.0_172] at sun.nio.cs.StreamDecoder.implRead(Unknown Source) ~[?:1.8.0_172] at sun.nio.cs.StreamDecoder.read(Unknown Source) ~[?:1.8.0_172] at java.io.InputStreamReader.read(Unknown Source) ~[?:1.8.0_172] at java.io.BufferedReader.fill(Unknown Source) ~[?:1.8.0_172] at java.io.BufferedReader.readLine(Unknown Source) ~[?:1.8.0_172] at java.io.BufferedReader.readLine(Unknown Source) ~[?:1.8.0_172] at sn$2.run(SourceFile:107) [server.jar:?]Code analysis
It seems that the reason for this is that the server can process commands provided from the command prompt (System.in) and independently from the JTextField. In case you do not start the server using the command prompt it still tries to read the input from it which is not possible. It appears that there is no way to prevent this because apparently System.in is not null by default and you cannot test if the readers can read without calling the reading methods and catching exceptions (which is the way it currently behaves).
As suggested in this StackOverflow answer the method InputStream.available() could be used at the start to detect if System.in is usable. If the .jar is not started from command line, then this method throws the exception as well. In this case a warning or an info message could be logged (including the exception?) and only the GUI input could be used.
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
Missing lines from your log, please post the complete output.
If you are receiving:
09:23:17 Server console handler/ERROR: Exception handling console input
then
Duplicate of MC-33041
Duplicate of MC-33041 - If you have not, please use the search function in the future, to see if your bug has already been submitted. If you could not find the original report, please comment with the keywords you searched for.
This still seems to effect 1.7.9, it's a pretty big bug. Renders the server exe useless, but running the server jar with java or javaw (see below) seems to work. This makes server setup on windows a bit less intuitive.
I wonder if this is related to MC-33041, which occurs when the server jar is run with javaw.
Dupe of MC-33041
Dupe of MC-33041
MC-33041 deals with blank console output when using server.exe which is not a game-breaking issue. This is the server itself failing to run due to a bug in 1.8 when handling old player.dat files from the previous version.
@Alex Darlow, the issue in your log is MC-33041, which has nothing to do with connection issues.
Duplicate of MC-33041. Either use the jar instead of exe launcher, or use a script to launch it with java instead of javaw.
Dupe of MC-33041
Dupe of MC-33041
Duplicate of MC-33041. This however is only an issue affecting the display of server console output in the server window. Any other issues should be investigated via support resources.
For technical support please use the Mojang Support Center.
Thank you for your report!
However, this issue is a Duplicate of MC-33041.
It has been linked to this report. If you have additional information, please add it to that report.
Please search before reporting, as it's likely that one exists already.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – 📖 Game Wiki
See MC-33041.
Thank you for your report!
However, this issue is a Duplicate of MC-33041.
If you have additional information, please add it to that report.
Please search before reporting, as it's likely that one exists already.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – 📖 Game Wiki
Thank you for your report!
We're actually already tracking this issue in MC-33041, so I resolved and linked this ticket as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature in the future to see if the issue has already been reported.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – 📖 Game Wiki
Thank you for your report!
We're actually already tracking this issue in MC-33041, so I resolved and linked this ticket as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature in the future to see if the issue has already been reported.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – 📖 Game Wiki
Thank you for your report!
We're actually already tracking this issue in MC-33041, so I resolved and linked this ticket as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature in the future to see if the issue has already been reported.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – ✍️ Feedback and Suggestions – 📖 Game Wiki
Thank you for your report!
We're actually already tracking this issue in MC-33041, so I resolved and linked this ticket as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature in the future to see if the issue has already been reported.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – ✍️ Feedback and Suggestions – 📖 Game Wiki
Thanks for the report! This appears to be a duplicate of MC-33041. If you didn't, you might like to enter a query directly into the main JQL input box (in Advanced search), because entering the word "Invalid" in the top right search box automatically defaults to the resolution rather than the text content. ![]()
Your whitelist file is not formatted correctly.
(The other error message is MC-33041 and can be ignored)
Thank you for your report!
We're tracking this issue in MC-33041, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
Thank you for your report!
We're tracking this issue in MC-33041, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support (Technical Issues) – 📧 Microsoft Support (Account Issues)
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automatically! The ticket was resolved by one of our moderators, and I left this message to give more information to you.
Please see MC-33041
Being able to join only using localhost is expected behaviour when self hosting a server. For anyone not on your wifi, they can join using your public IP

"[09:23:17] [Server thread/INFO]: Starting minecraft server version 13w41b
[09:23:17] [Server console handler/ERROR]: Exception handling console input"
I'm getting this also in a standalone 1.7.2 server (executed as .jar file)
Same problem here. But connecting on server works well.
my 1.7.2 server was working fine until recently. I can log onto it but friends cant now. my server log looks same as reported by others. I would like to add that my Mozilla Foxfire recently updated to 25.0(x86en-US) and I also have Mozilla Maintenance Service that updated on the same day, Nov. 5th. I tried changing security on my browser but it had no effect.
I've been seeing this error in the logs since I updated to 1.7.2. I am using the minecraft_server.1.7.2.exe file to run the server on a Windows 7 64-bit machine with Java 1.7.0_45 64-bit. I can confirm that I am able to login successfully to the server, as are other users.
The way the error reads seems to be related to the display; the log and chat portion of the window remains blank the entire time the server is running, but the logs actively update. Running commands from the server window works as it should, and the normal feedback for running commands from the server window appears in the log. Other than the log (and chat) not displaying in the server GUI properly I have not seen any issues that seem to be related to this error.
I attached the server start-up leading into the error below for reference:
[07:33:43] [Server thread/INFO]: Starting minecraft server version 1.7.2
[07:33:43] [Server thread/INFO]: Loading properties
[07:33:43] [Server console handler/ERROR]: Exception handling console input
java.io.IOException: The handle is invalid
at java.io.FileInputStream.readBytes(Native Method) ~[?:1.7.0_45]
at java.io.FileInputStream.read(Unknown Source) ~[?:1.7.0_45]
at java.io.BufferedInputStream.read1(Unknown Source) ~[?:1.7.0_45]
at java.io.BufferedInputStream.read(Unknown Source) ~[?:1.7.0_45]
at sun.nio.cs.StreamDecoder.readBytes(Unknown Source) ~[?:1.7.0_45]
at sun.nio.cs.StreamDecoder.implRead(Unknown Source) ~[?:1.7.0_45]
at sun.nio.cs.StreamDecoder.read(Unknown Source) ~[?:1.7.0_45]
at java.io.InputStreamReader.read(Unknown Source) ~[?:1.7.0_45]
at java.io.BufferedReader.fill(Unknown Source) ~[?:1.7.0_45]
at java.io.BufferedReader.readLine(Unknown Source) ~[?:1.7.0_45]
at java.io.BufferedReader.readLine(Unknown Source) ~[?:1.7.0_45]
at ll.run(SourceFile:78) [minecraft_server.1.7.2.exe:?]
Still happening in 1.7.4
Please, any solution?
I still have this problem, Have a solution yet?
Snapshot 14w03b also affected.
Additional comment: Tested starting the server using a .bat file "Minecraft Server Startup.bat" with the Java command "java -Xmx1024M -Xms1024M -jar minecraft_server.14w03b.jar" and this resolved the error message because the console received input. When I used "Javaw" to start the server the error occurred.
Still in 1.7.8! I hope they'll fix it soon.
Still affecting 1.7.9 it seems!
Edit: I wonder if this is related to
MC-38758found that on my pc there was a old version of java under c\windows\jre... and when i remove this file from there my bat started working again
Still present in 14w28a
Still present in 14w30b
I've had this probem go away and start up again. I assume you have forge installed.
I just fixed it AGAIN. Extremely frustrating, since you should do a few things to ensure this is not killing your server.
First; it makes you a new world named "world" when it sees your other world that has grown too much in some way for the jvm to handle it. Before I get into that let's cover this;
Delete the file 'world' it made then rename your favorite world as 'world'. I just did that and fixed my problem....
but wait!
You have server properties file; use it. Delete all extras like port number and all that. Now start minecraft using a profile 1.7.2 for example without forge until your world loads up. It should show up, even amplified, and if not follow next steps either way;
Now you're ready to change Java memory settings. (windows 7)
3 things;
1; if you've not set the right path to 32 or 64 bit inside path from environmental variables under computer prop then do. Save your old line incase you screw that up. This tutorial you can find elsewhere I wont get into that.
2;set java virtual memory. Do this under control panel/ programs and features/java/ now under java control panel click java tab then view button. Since I have 8gb of ram (find out your ram # by going to start, right click on computer, properties : to see installed ram) then I am using 4gigs of it for java. CLICK TWICE FAST on the empty spot under RuntimePara...
Enter "-Xms4096m" without the quotation marks ofcourse , assuming you have 8g ram.
1024m if you have 2gigs and so on, since 1024 megabytes is equal to 1gigabyte.
3;(optional) Creative a startserver.bat file using notepad to start up java making double sure your server will be able to handle as much as possible. These numbers you can tweek later just like the other one. Make a text file obviously and enter this;
@echo off
java -Xmx6144M -Xms4096M -jar minecraft_server.1.7.2.jar gui
...that will give you a ram window of 4g to 6gigs instead of 1 to 1 or whatever, but restarting any server might not work eventually until you change the variable inside java virtual machine as stated earlier.
I MAY experience this problem again when I begin running mods in Forge since it takes more memory yet. Part of this problem is actually worse than you might think;
A system using an older hard drive or just one with years of use could have chip errors in the hard drive. They'll always work but do slow down for whatever reason. ..so getting an sshd or sshd hybrid will change things drastically for minecraft.
9.7.2014 mikefromspace utube
Is this still a concern in the current Minecraft version 1.8.1 Prerelease 3 / Launcher version 1.5.3 or later? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.
Also, make sure your Java is on 1.8 or higher.
It's been a while since I've had to deal with this, but ;
1; I recall fixing it by using an older version of Java since the new one would not allow any use of forge which so far I've only used to run optifine since the microsoft purchase pissed off a major contributor who wrote world edit. I do run 'no more cubes' once in a while for fun but my guy gets stuck on terrain no matter what with that.
2; Using optifine not possible in 1.8 which is slow as the frozen puke it is without optifine and I'm using a quad core i7 920 with 11g ram and a 1gig nvidia gtx260 video card. Even with optifine I need to go 30fps. Why the default ram is 1gig is beyond ridiculous. WHY CAN'T this be adjustable , I mean the script would be like 1 or 2 lines long to fix it !
Minecraft 1.8 is a joke. It's for 5 year olds who don't want amplified which is nuts. I have an amplified server setup. It would never work in 1.8 and I've already put too much work into it.
Java 8 works fine for everything now. Wrong information on several ends. Also, this does not answer my question. Keeping it on "Awaiting Response".
I can confirm this, starting the server from the console did not fix it for me.
I just installed java 1.8 And I still have the problem.
Note that it doesn't happen on startup, but a couple of hours after the server started up.
I'm starting to wonder wether this is the same bug as I'm experiencing. This issue doesn't really have a good description so could someone tell me if the server is crashing for you as well? Here's the first part of my crash report.
[00:21:01] [Server console handler/ERROR]: Exception handling console input java.io.IOException: Input/output error at java.io.FileInputStream.readBytes(Native Method) ~[?:1.8.0_25] at java.io.FileInputStream.read(FileInputStream.java:246) ~[?:1.8.0_25] at ... the rest is just the same as the other reports providedI resolved this error for my 1.8.1pre3 / pre5 servers by disabled the Service for ReadyBoost on our Windows server machines. I noticed randomly windows was using 100% of HD resource read/write and was causing the server to "Run Behind" or just crashing I/O error.
4 days running since last maintenance & backup, with no crashing and minimal "Run Behind."
using startup bat:
"C:\Program Files\Java\jre1.8.0_25\bin\java.exe" -server -d64 -Xms3848M -Xmx3848M -jar minecraft_server.1.8.1-pre5.jar nogui
Reopened.
@Jesper the End: I assigned the ticket to you, please change it to fit the issue better.
This certainly was an odd bug which I never could track down. Eventually I did end up reinstalling the entire windows7 o.s. and have been running on a rented server instead, but for a short time I did manage to fix the problem accidentally, although it was a line of code inside windows itself which is found under the most advanced settings after right clicking on "computer" to view properties, advanced tab, performance- settings. The issue may have been caused by using too much or too little ram in part, but I suspect it was simply bad ram. I was running 11g using 8 or 10 at the time on the setting with 2 different ddr3 ram brands installed. Later I removed 3 of the 1g old sticks and now using only 2 of the 4g sticks (newer) which doesn't error as it did before when running other programs like a chrome browser with multiple tabs open for example.
I'll be re-testing the server by next weekend I suspect and will see if I can't re-create this problem.
Confirmed for
It seems that the reason for this is that the server can process commands provided from the command prompt (System.in) and independently from the JTextField. In case you do not start the server using the command prompt it still tries to read the input from it which is not possible. It appears that there is no way to prevent this because apparently System.in is not null by default and you cannot test if the readers can read without calling the reading methods and catching exceptions (which is the way it currently behaves).
Could you please link from the description to the comment above
Can confirm in 1.18.2.
Can confirm in 1.19.
Can confirm in 1.19.2 and 22w42a.