I have set the stream.management.active false and apparently it is working fine, will observe it for a while
This will indeed disable the Stream Management functionality in Openfire. Note however that you’re responding to a pretty old discussion. Stream Management issues in Openfire have been resolved in the latest releases.
unfortunately, it is not resolved but the frequency of this error is decreased, we are on 4.1.6 version , do you know how to completely resolve this issue without updating the version?
Openfire 4.1.6 was released in October 2017, more than three and a half years ago. That’s even older than the first message of this discussion!
Although I have not checked for this specific version, it is very likely that the version has bugs with regards to Stream Management that have been fixed in later releases. It therefor might be impossible to use Stream Management, without updating - although I can’t be sure.
I strongly suggest that you consider an upgrade scenario. Apart from this functionality, other important changes have been introduced in later versions.
If you cannot move away from this particular version, you could consider reaching out to one of the companies that provide paid support for Openfire, to see to what extend it is feasible to backport stream management fixes to a project that is based on Openfire 4.1.6.
Thank you for your reply. the problem is that we have the openfire which acts as a backbone of our large scale product and at least 1000 concurrent users connected and sending and receiving real time messages extensively, we used the latest version in our another big application and the result was devastated and at the end they have to restore the backups and later switch to signalR. So, that’s why we are afraid to update the openfire version.
I’m sorry to hear that. It sound like you have some challenges in the way Openfire/XMPP was integrated in your systems. That might warrant further investigation.
The fact that you’re using it in a large scale product is all the more reason for your company to consider working on an upgrade strategy. You’re now using old software that has known defects. That can’t be good.
1 Like
Thanks for you help. I am planning to upgrade the version on our UAT environment first.
One more thing if you can help that our company ethical hacker write a macro in which he can send unlimited number of messages on xmpp in no time, it can affects openfire server and database. please note that it is a public chat in which we cannot implement captcha and cannot authenticate the user before start the chat. Could we do anything to prevent this, We also restrict the CORS with our domains.
Thank you in advance.
I think that we’re well beyond the scope of this particular discussion thread. Can you create a new thread please?
Yes, you are right, i just created here Chat Flooding Prevention a new topic. Could you please check