Failed to set channel option 'CONNECT_TIMEOUT_MILLIS' with value '-1'

[TypicalModMaker]

Failed to set channel option 'CONNECT_TIMEOUT_MILLIS' with value '-1'

[Janmm14]

Your configuration is invalid. For safety, timeout shall NEVER be attempted to get disabled. Set timeout: 30000 in config.yml

Additionally it is highly adviced to NOT set network_compression_threshold: -1, instead I would suggest to set it to a value like 256 or 1024

[TypicalModMaker]

setting timeout to 60k doesnt fix this issue

[electronicboy]

You have multiple connection related timeout values set to -1, this is not supported behavior

[xism4]

Your configuration is invalid. For safety, timeout shall NEVER be attempted to get disabled. Set timeout: 30000 in config.yml

Additionally it is highly adviced to NOT set network_compression_threshold: -1, instead I would suggest to set it to a value like 256 or 1024

I think this is worth in local servers, I would use that amount if Netty's flush consolidator event is enabled and the servers are hosted on different locations.

[Janmm14]

Your configuration is invalid. For safety, timeout shall NEVER be attempted to get disabled. Set timeout: 30000 in config.yml
Additionally it is highly adviced to NOT set network_compression_threshold: -1, instead I would suggest to set it to a value like 256 or 1024

I think this is worth in local servers, I would use that amount if Netty's flush consolidator event is enabled and the servers are hosted on different locations.

Well... maybe, I'd say it depends on the capabilities of the OS to optimize localhost (tcp) connections.

No-recompress patch eliminates parts of the increased cpu load.
(And I recently created a small patch for someone involving a small edit of spigot as well which also eliminates decompression of packets bungee doesn't need to edit, which would make setting it to -1 actually worse.)