This forum has been archived. No new posts can be made and no new users can sign up. It remains here for reference only.
I'm running a heavy modpack and only clients with SSDs are fast enough to join the server. Everyone else times out. I've tested this in LAN mode and confirmed adding -Dfml.readTimeout=120 works great without issue. But on the server, it seems to do nothing as everyone keeps timing out while loading.
Not really something I can help with, I'd suggest talking to the mod developers in question. AMP provides the arguments you ask it but its involvement pretty much ends there.
I changed my timeout on the server and client to 300, or 5 minutes, and watched the timestamp of the logs. It's kicking the client's connection at 60 seconds, not 300 seconds. Something weird is going on.
[12:55:05] [Minecraft:admin Debug] : Java start arguments: -Xmx3072M -Dfml.readTimeout=300 -jar forge-1.10.2-12.18.3.2511-universal.jar nogui
[20:51:51] [Core:admin Debug] Â Â Â : Arguments: -Xmx3024M -Dfml.readTimeout=120 -jar forge-1.10.2-12.18.3.2511-universal.jar nogui
I found this in the logs. It looks like it should be applying. However, the user without an SSD keeps getting timeout messages. I also told them to add the same JVM argument to their client as well.
When I hosted this same server on my SSD computer and opened to LAN, the other user couldn't connect due to timeouts. When I set -Dfml.readTimeout=60 they could connect no issue.
I could try setting -Dfml.readTimeout=300 to set it to 5 minutes if you think that might work.
It just seemed like 2 minutes should be long enough of a timeout for connecting to the server.
Thank you for the quick reply!
Have you checked AMPs log to see if they're being applied correctly?
