Migration from Openfire 4.2.3 (windows server 2003) to Openfire 4.7.3 (windows server 2012)

Openfire
1

We are currently using Openfire 4.2.3 and XAMPP 1.7.2 (Windows Server 2003) with standard database connection setting (external database)
We will migrate it in separate server (Windows Server 2012) with Openfire 4.7.3 and XAMPP 8.16
As of now, I already exported our existing database and imported to new server. I already configured the Openfire 4.7.3 connected to it. See below my inquiry if I need to do it also:

  1. Do I need to migrate the schema database of our existing to our new server? If yes, please advise on how to do it
  2. Using Plug in (monitoring service 2.3.0), we can’t view the conversation history. it says “The messages in this conversation were not archived.” We installed monitoring service 2.2.0 and it works now but upon checking to openfire logs, there is an error below. How to fix it. thank you. I’am hoping for your held about this. thanks
Exception in thread "mysql-cj-abandoned-connection-cleanup" java.lang.NoClassDefFoundError: Could not initialize class com.mysql.cj.protocol.ExportControlled
	at com.mysql.cj.protocol.NetworkResources.forceClose(NetworkResources.java:53)
	at com.mysql.cj.jdbc.AbandonedConnectionCleanupThread$ConnectionFinalizerPhantomReference.finalizeResources(AbandonedConnectionCleanupThread.java:248)
	at com.mysql.cj.jdbc.AbandonedConnectionCleanupThread.finalizeResource(AbandonedConnectionCleanupThread.java:226)
	at com.mysql.cj.jdbc.AbandonedConnectionCleanupThread.run(AbandonedConnectionCleanupThread.java:93)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
	at java.lang.Thread.run(Unknown Source)
2
  1. Openfire will automatically upgrade the database schema when it boots up. You should not need to do anything manually. Generally, it is a good idea to have a backup available, and closely watch the log files during the first startup of the upgraded Openfire instance, for any indications of issues.
  2. I’m not sure what is causing the issue with the Monitoring plugin. The stack trace that you show might indicate that the version of the MySQL JDBC driver that is being used is not compatible / to old. This driver should be a .jar file in the lib directory of Openfire. Can you check if you are using the latest version that ships with Openfire 4.7.3? Also make sure that you don’t have multiple variants of that driver in the lib folder.
3

Hi Guus,
Thanks for your reply. Currently the error of the openfire now is below:
"Found old database version 4 for monitoring. Upgrade to version 6.0
Error while loading plugin “monitoring: Database update failed. Please manually upgrade your database”
How can I manually upgrade the database? thanks

image
image936×390 129 KB

4

Hi Guus,

  1. I tried to install monitoring service 1.8.0 plugin and there is know error already on Openfire (see below screenshot but I’m thinking why is it red in color?

    image
    image774×329 19.7 KB

  2. Is it OK to use this old version of monitoring service 1.8.0 plug in since the latest compatible version should be monitoring service 2.3.1 for Openfire 4.7.3?

Hoping for your reply. thanks

5

I’m not sure why that’s in red, but I don’t think that it indicates a problem.

Please have a look at the log files for Openfire. They will include the errors that occurred during the database upgrade.

You probably cannot run version 1.8.0 of the Monitoring service plugin. You will need a newer version. At the time when 1.8.0 was released, it was unknown what the latest compatible version of Openfire was going to be. Sadly, we have no mechanism in place to define such compatibility data for plugins that were already released in the past.

6

Hi Guus,
Monitoring Service plugin 1.8.0 is working on Openfire 4.7.3. I can view the conversation history without error on Openfire but there is only delay on the new conversation when viewing but the old conversation can easily view it. thanks