On Tue, Mar 02, 2004 at 01:08:29PM -0500, Bob Phan wrote:Out of curiosity does J1.4 suffer from this?
I've been trying to get j2 to scale. So far, I've been able to get about 8000 connections to the server before sm consumes about 3gigs of memory and then locks up the system. I'm fairly sure that 8000 connections doesn't _require_ 3gigs of ram, so there must be some kind of memory leak in the sm.
I'm curious if this is a known issue. Also, I'd like to be able to
help track down and fix whatever memory leaks may exist in the sm.
If anyone could give me any help as to where to begin or how to
go about this, it would help out a lot. I don't think blindly
diving into the sm code would be the best approach for this, so if
you know any sections of the code that may be linked to the sm
leakage, I'll start looking around there and try and patch up the
leaks.
j2 is currently pretty lousy when it comes to memory management. It
generally assumes that it can get as much memory as it wants. Certain
things (eg the JID cache) are never freed or cleaned up, and can grow
forever.
Dave.
_______________________________________________ jdev mailing list [EMAIL PROTECTED] https://jabberstudio.org/mailman/listinfo/jdev
