running openfire on debian wheezy x64 with oracle java 8 (userd to be 7)
Less than 20 users, usually there are ~5 people online. most are using android client xabber.
auth via LDAP, using mysql for DB
active plugins: monitoring for chat archive and kraken for irc/icq transport (only 2 people are using transports)
no BOSH or S2S connections, one MUC room.
had 3.9.3 running for almost a year, never had trouble.
when 3.10.0 was released I upgraded. Since the upgrade openfire rapidly gets to 100% cpu usage. Usually 2-3 days after staring the service it was so severe that the monitoring was raising alarms, openfire needed to be restarted.
yesterday I upgraded to 3.10.1. less than 24hrs later openfire is again causing 100% cpu load.
Now, I dont want to say it got worse but it sure diddnt get better.
Unfortunately I dont have any knowledge about debugging or java and have a hard time understanding the logs either so I seem not able to give much more information.
I just downgraded back to 3.9.3 because restarting openfire every few hours is a less favourable solution for me than running 3.9.3
But please, I would like to have a 3.10.x running stable and without eating up all my cpu power in the future. this problem seems to me to be somewhat common, so I have hope that we can get enough information that it can and will be fixed soon.
Fixing this is very high priority, our current thought is to downgrade the bundled MINA to version 2.0.7 and Tom has prepared a pull request to do just that.
OF-922: Revert MINA to 2.0.7 by tevans · Pull Request #241 · igniterealtime/Openfire · GitHub
We just need some testing of this patch to see if it breaks anything else in the process.
