A little background: We’ve been running Openfire 3.6.3 at my company with moderate success for around a month, and generally peak during the day at around 200 users. We are using LDAP for authentication/group management, but are considering moving to mysql instead to bring it all ‘in house’, as it were.
I saw that Openfire 3.6.4 introduced a fix for a bug that would allow users to change another user’s password, so I included the upgrade in a scheduled off-peak maintenance. After following the upgrade guidelines (stopped the service, backed up the db/app, and ran the installer), I noticed immediate performance issues. First, it took several minutes to be able to log in via a client, recieving a message stating that the server was not responding. I was able to log in to the admin console almost immediately. After the server was available for clients, sessions begain appearing, but were all displayed as ‘offline.’ No users on any rosteres were available in the clients. We were no longer able to add/remove users to our rosters, or search for a user. Performance for client-to-server traffic was unacceptably slow. I assumed the server was updating the list of users, or something, in the cache. I allowed it to run for approximately 3 hours, before I finally made the decision to roll back to 3.6.3-- when I did, the system returned to normal, and has remained so ever since.
I have not been able to find anyone else mentioning issues, and I will be loading Openfire in to my dev environment to attempt to identify the issue. Has anyone else experienced similar issues, and were you able to resolve them?