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 likely introduced by .
Since migrating from MINA to Netty (OF-2559) the IgniteRealtime server uses Netty to establish an outbound server-to-server connection.
The corresponding handler uses an event listener to call a stop routine when a channel is closed. However, under circumstances, Openfire also calls that stop routine directly. As this closes the channel, stop is invoked by the event handler again.
The code should be improved to guard against trying to stop things more than once.
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 likely introduced by .
Since migrating from MINA to Netty (OF-2559) the IgniteRealtime server uses Netty to establish an outbound server-to-server connection.
The corresponding handler uses an event listener to call a
stoproutine when a channel is closed. However, under circumstances, Openfire also calls thatstoproutine directly. As this closes the channel,stopis invoked by the event handler again.The code should be improved to guard against trying to stop things more than once.