powered by Jive Software

Group Chat - DB Table Cache - ofMucConversationLog

Hi everyone,

We’re looking to create a unique configuration load-balanced solution for Openfire using database merge replication.

We’ve run into a snag, in a failover situation the chat group history isn’t showing up in the client even though the data exists in the SQL DB. What we’ve determined is the Openfire server caches the contents of the ofMucconversationlog in memory vs loading it from the SQL DB.

If at all possible I’m looking for feedback from anyone who knows about the process involved with group chat and the database or a method for me to reload the database table with current content into memory.

Thanks

Jeremie