Ok, thanks. I was wondering if I really needed to introduce ping-pong into my protocol, just to keep it alive. Guess maybe I have. But at least using Netty 4.1.21.Final I am now notified when the connection is closed, so that I can reestablish. Just to get it clear, is it the OS or involved network (routers or whatever) that shots down the connection (after 2 hours of inactivity), despite adding SO_KEEPALIVE, or is it Netty that does it?
Den fredag den 16. februar 2018 kl. 09.23.38 UTC+1 skrev Norman Maurer: > > The only “safe” way is to have your application send some kind of “keep > alive” messages from time to time. SO_KEEPALIVE is not really good enough > for this. > -- You received this message because you are subscribed to the Google Groups "Netty discussions" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/netty/9b8dbe16-846d-4647-b12f-a9b48eead746%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
