A fix for this problem is now available in our nightly builds of Openfire (starting with the one from June 18’th). The fix has several aspects:
- it should further guard against additional bloat (redundant pubsub subscription records) being introduced (although there are indications that this was already stopped by other changes that went into Openfire 5.1.0)
- it reduces the memory footprint of each of the records (reducing the chances of having memory issues when they are all loaded into memory)
- it stops loading redundant records from the database (not loading all the bloat should significantly reduce resource usage
- a new maintenance task is introduced, which allows an administrator to perform a one-shot action, to clean up all redundant records from the database. This looks a bit like this:
Although we’ve tested these fixes in a number of environments, it would be very helpful to get feedback from people in this thread - especially those who have experienced the issue first-hand.