Race condition during cluster initialization (Hazelcast plugin)
Cache initialization issues during cluster startup. See community post for details.
Hi, I'm not allowed to create an issue, or I don't know how to do it.
I have a question for @Tom Evans - or whoever can answer: https://stackoverflow.com/questions/52524231/openfire-with-hazelcast-clustering-plugin-session-is-not-shared-candy-chat-not
We have Candy JS chat with two OpenFire 4.1.7 nodes sitting on LAN with Hazelcast clustering plugins. Plugins are set up to connect using tcp-ip and see each other just fine. Both OpenFire nodes are set to use the same SQL Server database.
I searched for that error and found it in OpenFire source code at https://github.com/igniterealtime/Openfire/blob/master/src/java/org/jivesoftware/openfire/http/HttpBindServlet.java. From comments there it looks like that error means Sessions are not shared between OpenFire servers.
Is such setup supposed to work? Any ideas of what is wrong? I hope that sticky sessions are not required....
@Tom Evans, The link is up on the websitehttp://www.igniterealtime.org/projects/openfire/plugins.jsp, and I see the page now magically fixed itself for the bug I was seeing, sigh....
Ignite's cluster is no longer running. We had too many issues with spammers
Would be great if we could set this up this new build for dogfooding on the Ignite cluster. Let me know if can can be of any assistance.
@Tom Evans, strike that last comment, for some reason, the website did not like this updated plugin. Still investigating...