Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Closing S2S session fails to close outbound

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 .

When a server session is closed on the admin console, only the inbound connection (if any) appears to be closed.

For sessions that have both an inbound and an outbound connection, only the outbound connection remains

For sessions that only have an outbound connection, nothing appears to change.

In both cases, the security audit log happily reports that the session is closed.

Environment

None

blocks

Activity

Show:

Guus der Kinderen 
September 4, 2023 at 7:17 PM
(edited)

I’ve closed this, as I’m pretty sure that this is an artifact of incorrect streams. This partially has been addressed by a recent commit, but still happens as a result of issues and possibly .

Guus der Kinderen 
August 31, 2023 at 6:21 PM

I wonder if this relates to which is another issue that describes an oddity with outbound Server-to-Server connections.

Fixed

Details

Assignee

Reporter

Components

Fix versions

Priority

Created August 31, 2023 at 6:02 PM
Updated September 6, 2023 at 11:02 AM
Resolved September 4, 2023 at 7:13 PM