Diego,
The particular memory "leak" you are seeing is the effect of the Avalon
Scheduler. It isn't so much a leak as uncontrolled growth in the
scheduler's priority queue. The next milestone build will eliminate that
issue. There are also other memory leaks. My first goal is to get the
SMTPHandler such that its own internal processing is clean. That has not
been the case until some time late last night / early this morning.
As of now, I have a private test build that runs between 30 and 50 messages
per second without any apparent memory leak in the handler. I can't say
what will happen once the spool is re-engaged, but one step at a time.
Still some work to do in the handler area.
--- Noel
--
To unsubscribe, e-mail: <mailto:james-user-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:james-user-help@;jakarta.apache.org>
