Netty idle state detects mixes 'read' and 'write' idle events

Description

This issue affects a version of Openfire that is as of yet unreleased. It should not affect anyone running a proper release of Openfire. It is introduced by .

It appears that the replacement code for MINA’s idle state detection in Netty mis-matches ‘read’ and ‘write’ events.

The old code intends to send a ping request at half the maximum idle time, to close the connection if the connection remains idle for another half max time. This is both based on the ‘read’ idleness, reflecting data received from the peer.

New code uses a similar approach to pinging at half the idle time on which a connection is closed, but relates these to two different events: an ‘read’ idle event, and a ‘write’ idle event.

Instead, all events should be tied to the ‘read’ idle event.

This issue might be the cause of the regular client disconnections that I’ve been experiencing since moving to the new Netty code.

Environment

None

relates to

Activity

Show:
Fixed

Details

Assignee

Reporter

Fix versions

Priority

Created October 26, 2023 at 12:56 PM
Updated October 26, 2023 at 3:16 PM
Resolved October 26, 2023 at 3:16 PM