Oh, silly me. I should have read the javadoc of course. Ok that is useful info, thanks.

Ah, that sounds helpful.
I set the logging levels to trace, and yes. I can see "com.esotericsoftware.kryo.SerializationException: Buffer limit exceeded writing object of type..." at com.esotericsoftware.kryo.Kryo.writeClassAndObject(Kryo.java:483) now.
I tried to set larger bufferSizes for server and client (32768, 16384). It helped, but it also increased the latency terribly. Or maybe not the latency because the whole game is getting frozen every second or two.
EDIT : ah, nevermind, that was caused by large amount of logging output. So it seems to be working.
Are there some recommanded values ? Or is there some approach I can take to this ? I can set the values higher, but still, it may happen, that they will overflow. Is there some solution to this situation ?

Well of course that could be the problem, but that does not answer my question. I can't just arbitrary cut down the traffic to some magic number and then expect this problem won't occur again. I would expect that if the network can't keep up, that it will try to do it's best. Of course the messages will start having delay end eventually I may get some timeout or buffer overflow or whatever. On the other hand it may be a peak traffic which will calm down in few seconds and then it should catch up.
But I need some information, that the network is not able to handle the traffic. Not just plain "client disconnects".

In another words - it seems logical to expect from a network layer/library to deliver all the data I provide. I can understand that when I give 200kB of data on a 50kB connection it will take at least 4 seconds to send it. But I don't expect the answer "nope, I can't send 200kB" :-)

Hi,
I have a question to kyonet lib. It seems to have problems with handling both large and numerous messages. When I send to many messages per second (hundreds) or some messages with a lot of data, the client just disconnects from the server. There is neither an exception nor an error message.
How am I supposed to prevent or handle this ?