Skip to:
I updated from Openfire 4.7.5 to 4.8.0 and observed the following change.
With Openfire 4.7.5:
My client would send “white space pings” (sending a simple space character) every minute and not respond to server requested pings
Client would stay connected
With Openfire 4.8.0
My client would send “white space pings” and this would not count as session activity
The client gets disconnected with
Updating the client to formally respond to the pings, is of course the right thing to do here, but am denoting the change in behaviour.
There is this comment in NettyIdleStateKeepAliveHandler:
NettyIdleStateKeepAliveHandler
Note that whitespace pings that are sent by XMPP entities will also cause the connection idle count to be reset.
This clearly indicates that the intent was to retain the ‘whitespace ping’ functionality in 4.8.0.
I updated from Openfire 4.7.5 to 4.8.0 and observed the following change.
With Openfire 4.7.5:
My client would send “white space pings” (sending a simple space character) every minute and not respond to server requested pings
Client would stay connected
With Openfire 4.8.0
My client would send “white space pings” and this would not count as session activity
The client gets disconnected with
Updating the client to formally respond to the pings, is of course the right thing to do here, but am denoting the change in behaviour.