Build: #1911 did not complete Manual run by daryl herzmann

Stages & jobs

  1. Build and Package

  2. Copy to Website

Build result summary

Details

Queued
Started
Completed
Status
Reason for not building is unknown
Labels
None
Revision
89722b7d5be186bca4b13001ddeb702cc8b95eeb

Code commits

Author Commit Message Commit date
daryl herzmann <akrherz@iastate.edu> daryl herzmann <akrherz@iastate.edu> 89722b7d5be186bca4b13001ddeb702cc8b95eeb Merge pull request #2384 from akrherz/480ga
Denote Openfire 4.8.0 Release
akrherz <akrherz@iastate.edu> akrherz <akrherz@iastate.edu> 7e0a5d0f527797c1efe27a20b99acf95e5aec841 Denote Openfire 4.8.0 Release
Guus der Kinderen Guus der Kinderen 0ca36fbb3c97c892b417fcb8343b022340039366 OF-2755: Fix bug in cluster cleanup code
When a cluster node leaves the cluster, cleanup code is executed. Part of this code is a check that verifies if a certain cache contains entries for each incoming server session. This compares incoming server sessions from another data structure with the content of that cache.

This code previously assumed that there could only be one session per remote domain, which is a false assumption. Moreover, it didn't properly verify the StreamID value.

The assumption in the old code causes an exception to be thrown, which prevents the 'left cluster' event from being finished completely, leading to state inconsistencies.

Although it is likely unexpected that Openfire maintains multiple sessions per remote domain, having more than one is entirely feasible. The code should allow for this.
Guus der Kinderen Guus der Kinderen 1a693d4d6623482eae2d214dc5ea25d81d8e158b OF-2770: Add debug logging to Pub/Sub
The Pub/Sub implementation had hardly any logging. This makes analyzing issues hard.

In this commit, copious amounts of trace logging has been added.

A couple of mostly trivial code changes were applied (mostly IDE suggested improvements).

Jira issues

IssueDescriptionStatus
Unknown Issue TypeOF-2755Could not obtain issue details from Jira
Unknown Issue TypeOF-2770Could not obtain issue details from Jira