The Ignite Realtime community is happy to announce the release of version 3.8.0 of Openfire! Downloads for various platforms are available here.
Openfire is a real time collaboration (RTC) server licensed under the Open Source Apache license. It uses the only widely adopted open protocol for instant messaging, XMPP (also called Jabber). Openfire is incredibly easy to setup and administer, but offers rock-solid security and performance.
This release accumulates development efforts made over the past fifteen months. Some highlights of this release are:
the new Hazelcast-based clustering plugin (subject of an earlier blog post)
substantial improvements to the functionality, scalability and stability of the PubSub implementation (including fixing the PEP related memory leak)
improvements of the server-to-server connectivity routines
many performance improvements and general bug fixes
The changelog lists these and other changes in more detail.
As always, we welcome your feedback, suggestions, tips, hints, questions and other contributions in the Ignite Realtime Community pages.
Thatās awesome, I canāt wait to try it out. Iām a bit new to all of this but Iām learning quick and having an absolute blast along the way. Thanks for all of your hardwork.
Congrats on a new release I thought JIRA went insane today with all the updates on tickets Good to hear about memory leaks being fixed, though i probably wonāt be able to test it myself, as i have already bumped the JVM memory and restart the server monthly for a backup.
Yeah! Finally! One small question: which java version performse best w/ v. 3.8.0? Will it install any new version? āfixing the PEP related memory leakā (finally and forever) is like heaven sent for me
Please be aware that an important issue was raised, that might affect Openfire 3.8.0 instances that are backed by an LDAP (or otherwise āread-onlyā) user store. More details on this potential issue can be found in OF-610.
A preliminary fix for the issue was implemented, and is available for testing in the nightly builds, starting from the ones generated on February 7th.
I exprienced that using wordpress as my user store, but assumed it was something I did in my code that was causing that. Thanks Guus for revealing that. That would have cost me days of debugging.
A big thank to all the contributors especially Tom and Rob for their work on pubsub clustering. It has made a difference