Stefano Bagnara wrote:
> Noel J. Bergman wrote:
> > Unfortunately, I once again confirm (this time using the embedded
memstat
> > check in RemoteManager) that we are losing about 2MB per day. And it
does
> > seem related to the days, not the amount of mail.
> Imho the memstat showing 2MB more every day in an "uncontrolled"
> environment is not a clear sign of a leak. Maybe you simply have
> increase in traffic or anything else.. Imho this will be "confirmed"
> when we'll be able to reproduce it in a different environment.
An increase in traffic would not result in a consistent ~2MB per day
decrease in available heap space after a GC. By definition, memory that is
consumed and not released is a memory leak.
> Why can't you send your config.xml?? Just remove sensitive
> informations and let us work on this bug!
When I have a sufficiently large round tuit to edit over 100K of config
info, I will. I'd have to sanitize domain names, list names and e-mail
addresses.
> I again wonder about the memory consumed by those Phoenix artifacts that
> showed up in the prior logs. Considering that both Stefano and Norman run
> with larger heaps than I do,
> I just ran a postage test and I cannot confirm this idea.
> 1) I changed environment.xml to rotate logs *every* *second*
> 2) I changed Xmx to 10MB (10!!!)
> 3) I create a test configuration for postage to run 30 minutes of low
> costant traffic:
I'll try to get a chance to run with heap profiling late this week. I'll
increase and track the heap size to make sure that I can get a few days
worth of heap site records.
> Imo it does not make sense to document the issue until we are able to
> reproduce it somewhere else and we will understand WHERE is the leak.
<<shrug>> There is a memory leak. We don't know where it is, but unless it
is still in Connector/J or in the JDK, it is in JAMES code, since I run only
JAMES code plus Connector/J.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]