Error when standalone Openfire checks for timed out users
Description
After a time has passed, Openfire checks for timed out users. When running a standalone instance of Openfire running in Docker, I observed this in the logs: Given the references to DefaultCacheStrategy, suspect something we've done recently for MUC in clusters has broken this for MUC not in a cluster.
Environment
None
Activity
Show:
Guus der Kinderen November 10, 2021 at 2:18 PM
I think this got introduced by , which introduces an invocation of the tryLock method on a cache. That’s an optional operation. I don’t see why it can’t be implemented for non-clustered caches though.
After a time has passed, Openfire checks for timed out users.
When running a standalone instance of Openfire running in Docker, I observed this in the logs:
Given the references to DefaultCacheStrategy, suspect something we've done recently for MUC in clusters has broken this for MUC not in a cluster.