> We are using the Red Hat application, TOP, to view system resources
That doesn't necessarily tell you anything useful about the application's
use of memory, although continuous heap growth would be a concern.
> We saw the heap grow, but did not take into account that perhaps JAMES
> was not using the entire heap.
Depending upon JVM and tuning parameters, the memory reflected by TOP will
take into account the maximum heap, but not the actual heap currently used.
> you have no idea the relief that I had when you wrote back stating
> that you were unaware of any memory leaks! What a terrible thought
> of having the fault lie within JAMES. We could always rewrite
> mailets, but not JAMES.
We CAN rewrite James, and if there is an undetected leak, we'll fix it once
it is identified. I fixed a lot of memory leaks last Fall, prior to James
v2.1 release.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
