Increase MUC idle kick default value to allow for SM
Description
To detect ‘ghost users’ (users that appear to be active occupants, but in reality are no longer connected), Openfire will, by default, send IQ ping requests to occupants that are idle every 8 minutes. If no response is received within a certain timeout (currently coded to be 25% of the idle interval), the user is deemed ‘a ghost’ and is removed from the chatroom.
It has been noticed that this strategy often leads to occupants being removed that are, in fact, not ghosts at all.
A common occurrence is that the above removes occupants that are currently in a ‘detached’ state of stream management, as this state allows them to be unresponsive for a duration that typically spans several minutes (Openfire by default allows for up to 10 minutes of inactivity).
Openfire’s default ‘idle kick’ configuration should be lenient enough to not cause problems for these users. To do this, it should only kick occupants from a room when they are not responding to a IQ Ping after a duration that is at least equal to commonly used stream management detach timeouts.
Note that MUC rooms can contain users from remote domains: making this time-out a direct relation to Openfire’s stream management configuration is not safe.
To detect ‘ghost users’ (users that appear to be active occupants, but in reality are no longer connected), Openfire will, by default, send IQ ping requests to occupants that are idle every 8 minutes. If no response is received within a certain timeout (currently coded to be 25% of the idle interval), the user is deemed ‘a ghost’ and is removed from the chatroom.
It has been noticed that this strategy often leads to occupants being removed that are, in fact, not ghosts at all.
A common occurrence is that the above removes occupants that are currently in a ‘detached’ state of stream management, as this state allows them to be unresponsive for a duration that typically spans several minutes (Openfire by default allows for up to 10 minutes of inactivity).
Openfire’s default ‘idle kick’ configuration should be lenient enough to not cause problems for these users. To do this, it should only kick occupants from a room when they are not responding to a IQ Ping after a duration that is at least equal to commonly used stream management detach timeouts.
Note that MUC rooms can contain users from remote domains: making this time-out a direct relation to Openfire’s stream management configuration is not safe.