I apologize that this even happened in the first place... pah! It's eclipse's fault, for apparently working despite the bug ;-)
Explanation:
When a timeout is set on a Socket, then by documentation the read(...) call throws an exception if it doesn't receive data in time.
eclipse instead just silently returned 0 bytes without throwing an exception, thus I forgot to add the necessary try-catch block.
For now I cannot try this change with eclipse, so I do hope that eclipse at least won't complain about the catch...
mabe02
commented
3 years ago
I apologize that this even happened in the first place... pah! It's eclipse's fault, for apparently working despite the bug ;-)
Explanation:
When a timeout is set on a Socket, then by documentation the read(...) call throws an exception if it doesn't receive data in time. eclipse instead just silently returned 0 bytes without throwing an exception, thus I forgot to add the necessary try-catch block.
For now I cannot try this change with eclipse, so I do hope that eclipse at least won't complain about the catch...