Unresponsive clients cause Openfire to run out of memory


Openfire runs out of memory if unresponsive clients are connected.

Community discussion at http://www.igniterealtime.org/community/message/196900#196900




Guus der Kinderen
November 17, 2009, 2:55 PM

Although the issues where raised in the the same thread, they are indeed very different issues. Wroot is right: we are tracking the Empathy related issue in OF-82.

November 17, 2009, 2:53 PM

are you sure that the two issues are not linked? If you read the community discussion linked to this issue http://www.igniterealtime.org/community/message/196900#196900 it seems to affect lots of people after starting to use Empathy. Perhaps the two issues should be merged.


November 17, 2009, 2:42 PM

Matteo, this ticket is not related to Empathy issue. And it is already closed. Check

November 17, 2009, 2:32 PM

I would not decrease the priority of this bug. We have been running Openfire for about 2 years now and on the weekend we had huge issues due to someone deciding to connect with the new version of the Empathy client (Ubuntu default). I tried all the possibile memory configuration (from the default one to 1GB of heap space increasing as well the memory of the server to compensate for the increase in Java usage), but nothing helped. As soon as I blocked the IP address of the user connecting via Empathy I could put back the standard 128MB of heap space, but of course it's just a temporary solution.

This is a very critical bug for us and it's probably going to become very critical for more people as soon as users upgrade to the newer Ubuntu.

Guus der Kinderen
November 17, 2009, 3:07 AM

I'll leave the timeout patch in the code. I recently discovered StalledSessionsFilter which provides similar functionality - it kills idle sessions, based on traffic to-be-sent. My patch uses a timeout, the filter uses an amount of bytes queued to trigger the 'stalled' condition. Both solutions will work nice together.



Guus der Kinderen


Guus der Kinderen