Openfire becomes unresponsive every 15-20 minutes

At my business, we use Spark 2.6.3 and Openfire 3.7.1. Our Spark will become unresponsive and lose connection with all clients, disconnecting some and others have their lists sit there with no change till they attempt to msg someone. When the user attempts to re-connect it will say incorrect username and password even though the credentials haven’t changed. To fix this, we have started stopping the service and restarting it. Although, there is an error when we attempt to stop the service so we have to go into Task Manager and kill the process and then start the service afterwards. This fix will last for about 15-20 minutes before it happens again. If we attempt to access the web GUI, it will come up as “Page not accessible”.

In an attempt to fix this issue, we have updated the Java on the server, performed windows updates and looked into updating the Openfire server. We attempted to update to the 3.10.1 version, which I believe is the current version, and after following the instructions of installing overtop of it, the server will then not start.

Luckily we have made backups of our original install of the Openfire server but without being able to update to the new version we’re not sure what else we can try. Although we also read that we would have to update Spark to use the newer version of Openfire, which is another issue but until we can figure out how to update is mute. W

My questions are as follows:

1.) Is there a way to get this unresponsiveness to stop without having to upgrade?

2.) Does anyone know if I can jump distributions from my current Openfire 3.7.1 straight to 3.10.1 or do I need to step them?

3.) Does anyone know the correct procedure to upgrade Openfire? (There are no procedure’s on this site for upgrading)

I have the same problem and the same versions of Spark 2.6.3 and Openfire 3.7.1. I’m using Linux Debian 7 with kernel 3.2.0-4-amd64.

It happens exactly every 15 minutes and I think it is something related to Java because it uses 100% of the CPU for a few seconds, time enough to disconnect all the clients.

We ended up completely uninstalling openfire and reinstalling the latest version. On our systems, Java used up all the memory and then it became unresponsive.