Hi, maybe it’s in the cache.
If the cache is too small, then Openfire accesses the database more often and because of this the processor load may increase.
Attach a screenshot of your Openfire “Cache summary” cache page
Then it’s clear why everything is hanging on you.
Add these parameters to the console and reboot Openfire
cache.Roster.size -1
cache.User.size -1
cache.VCard.size -1
cache.group.size -1
cache.userCache.size -1
cache.username2roster.size -1
cache.vcardCache.size -1
Try to give more Java memory.
Here is a screenshot of how to do this on Windows Server.! 2019-08-07_10-03-34|690x356
But my advice is to install a clean Openfire 4.4.0 (x64), then install the latest Java JRE 8 or 11 and install MS SQL 17 Express and create a new database for openfire.
If you mean thorough testing by developers on every OS for every release, then no. There are only a few folks (most often one man) doing something here in their part time.
Btw, there is a new plugin called Thread Dump. Maybe it will provide a more useful debug info, although i see you already provided one before.
Openfire 3.8.1 on Java 1.6 ? That is not what your original post said. Please share a screenshot showing you using modern versions of Openfire and Java.