-
Bug
-
Resolution: Duplicate
-
None
-
Minecraft 14w07a
-
None
-
Minecraft Version: 14w07a
Operating System: Linux (amd64) version 2.6.18-348.16.1.el5
Java Version: 1.7.0_01, Oracle Corporation
Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation
Memory: 1904803328 bytes (1816 MB) / 4268228608 bytes (4070 MB) up to 4268228608 bytes (4070 MB)
JVM Flags: 3 total; -XX:MaxPermSize=192m -Xms4096M -Xmx4096M
IntCache: cache: 0, tcache: 0, allocated: 12, tallocated: 94
Profiler Position: N/A (disabled)
Player Count: 1 / 20; [oe['svengast'/605804, l='world', x=1888.98, y=175.00, z=3205.54]]
Is Modded: Unknown (can't tell)
Type: Dedicated Server (map_server.txt)Minecraft Version: 14w07a Operating System: Linux (amd64) version 2.6.18-348.16.1.el5 Java Version: 1.7.0_01, Oracle Corporation Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation Memory: 1904803328 bytes (1816 MB) / 4268228608 bytes (4070 MB) up to 4268228608 bytes (4070 MB) JVM Flags: 3 total; -XX:MaxPermSize=192m -Xms4096M -Xmx4096M IntCache: cache: 0, tcache: 0, allocated: 12, tallocated: 94 Profiler Position: N/A (disabled) Player Count: 1 / 20; [oe['svengast'/605804, l='world', x=1888.98, y=175.00, z=3205.54]] Is Modded: Unknown (can't tell) Type: Dedicated Server (map_server.txt)
-
Unconfirmed
Players who cannot connect to the server should not affect it's performance, even when spamming with failed login tries.
Players who for any reason (auth servers or session servers down, ban, not on whitelist, having client side issues) cannot log in and still tries to do so repeatedly causes a server crash.
To reproduce:
1 Create a server
2 Turn on whitelist
3 Make sure you're not on whitelist
4 Repeatedly and rapidly try to connect to the server
5 After 5-15 failed logins the server should crash.
First I am sorry for posting yet another duplicate, but if this is not correctly identified and makes it to full release and gets known to the public there will be outrage since every banned kid will crash the server they were banned from. The problem is already big enough for me to not be able to continue using 14w07a on my server to help identify other bugs.
I originally posted my findings in MC-48489 which was later categorized as a duplicate of MC-48411 which erroneously identifies slime blocks as causing the crashes and of course has not been confirmed, since slime blocks seem to work just fine on servers except for the shadow.
- duplicates
-
MC-48411 java.lang.NullPointerException: Exception in server tick loop
- Resolved