Hey Marcin, I'm curious to hear from you why do you think so? I absolutely agree that MINA has to provide easy ways to handle OOM problems due to heavy incoming or outgoing traffic.
This is by far the more common problem people are reporting with Openfire now that we moved to MINA (when under heavy load). Regards, -- Gato -----Original Message----- From: Marcin Waldowski [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 25, 2007 12:58 PM To: [email protected] Subject: Re: Permanent solution for OOM errors Hi, Trustin Lee wrote: > Hi Vinod, > > On 4/25/07, Vinod Panicker <[EMAIL PROTECTED]> wrote: >> Hi, >> >> I think we've already got a lot of issues on the list regarding OOM >> errors. In reality, every server needs to be able to manage I/O >> efficiently to avoid high memory utilization, which ultimately results >> in an OOM. >> >> What can be done? MINA Connectors and Acceptors need to have the Read >> and Write throttle filters by default. Once the specified buffer size >> per session / overall has been exhausted, MINA needs to shift into >> blocking mode to avoid an OOM on the server. > > Very true. I agree with you absolutely. I think we need to > incorporate this feature into the Acceptor / Connector > implementations. We could add some hook methods to > AbstractIoFilterChain, but I didn't try it yet. (probably after honey > moon ;) > I think that this is great idea. But I have second thoughts. Are we sure that we are not thinking about something which we will regret like ThreadModel? Regards, Marcin
