Memory Leak in 3.7.0?

I upgraded our Openfire server from 3.6.4 to 3.7 and since then every week or so the server runs out of memory and must be rebooted. Running on Redhat 5-32bit server, using the startup script, with java 1.6_0.16. Had 1gb allocated, then upped to 2gb when the problems started but didn’t have any effect. It acts like a leak, where it just steadily grows until there’s nothing left. We have about 130 users all running Windows 7 with Pidgin. We don’t run any plugins, and are using the embedded-db.

Any suggestions, directions on what to do next? Any help would be appreciated

I’m having a similar problem, but my users are connecting via http-bind. My theory is that the sessions are not being cleaned up correctly and literally just sit in memory, but I’ve been unable to find the problem in the code.

One of the announecements on top of the forums says:

Announcement: Suffering from memory-related issues in Openfire? Read this!

Openfires up to and including version 3.6.4 (and looks like 3.7.0 too) suffer from a memory leak in its PEP component. If your Openfire domain is crashing with OutOfMemoryExceptions, you might be having this problem.

As a workaround, you can disable PEP, by setting the Openfire property xmpp.pep.enabled to false.

Hi Garth,

Your theory is right. I believe the issue is with HTTPConnection.isClosed. This is getting set without the session.close() getting called. Figuring out a proper fix is a challenge for me.

daryl

I’ve done this and the server is still crashing.

2011.05.06 12:19:49 Error for /http-bind/

java.lang.OutOfMemoryError: Java heap space