Any version of Java equal to or higher than version 17 should be fine. I do not expect that a different version of Java will have a major impact on memory usage.
I am using my old Openfire 4.9.2 & JDK installed in my RHEL server as
opt]$ java -version
openjdk version “11.0.25” 2024-10-15 LTS
OpenJDK Runtime Environment (Red_Hat-11.0.25.0.9-1) (build 11.0.25+9-LTS)
OpenJDK 64-Bit Server VM (Red_Hat-11.0.25.0.9-1) (build 11.0.25+9-LTS, mixed mode, sharing)
[webadmin@AVN-ITG-Openfire_4_7_3 opt]$ openjdk version “11.0.25” 2024-10-15 LTS
Thats is working fine and now i have inetegrated new openfire 5.0.0 & with new downlaoded and kprt in opt folder JDK 17 after 1 week and CPU usage & memory is almost 100 %
You are using the embedded database, which gets loaded in memory completely.
For large Openfire instances, it is recommended to use one of the other database types that Openfire supports (like Postgres, SQL Server or MySQL).
I’m not sure why your database is so large. You could use the dbaccess plugin, or external tools, to inspect the database. Perhaps you can clean it up to save on size.
If I don’t want to use the other DB because for the last 8-9 years we were using the same DB, and after upgrading to Openfire 5.0.0, an issue occurs.
Well, I shifted back to the old version, 4.9.2, and still it is working fine.
I can see in the embedded DB folder openfire.script, openfire.log, & openfire.lobs. These files are growing large in number, which was not seen in previous versions.
Try creating or updating the property with the name provider.pubsub-persistence.className to value org.jivesoftware.openfire.pubsub.DefaultPubSubPersistenceProvider. You need to restart Openfire afterwards.