Stefano Bagnara wrote:

> Noel J. Bergman wrote:
> > The memory leak is documented and consistent.  The fact that you cannot
> > reproduce it is good, since perhaps it won't effect too many others, but
> > does not mean that it doesn't exist.  The empirical data doesn't lie:
every
> > day, there is ~2MB less memory available on the heap, which is
consistent
> > with what I have been seeing since I first reported the problem.

> I don't say that James has no memory leaks. I simply say that GC does
> not guarantee to garbage every unreferenced object. GC in modern JVM is
> much more complicate and the JVM doesn't even ensure you that a GC will
> ever occour when you call Runtime.gc() method.

Yes, but ~2MB per day would be an error in the GC if it existed, not some
casual happenstance.  Java's very language model is predicated upon
effective garbage collection.

> I say that is weird that your system works with 1.4.2_09 and not
> with 1.4.2_12 or 1.5.0_08: you know that Sun put much more
> attention than US in compatibility between versions.  So I wonder
> what does your system have so special to change behaviour (worse)
> upgrading a minor release for 1.4.2_09 to 1.4.2_12.

Ah ... now I understand.  It probably works fine in production.  What
surfaced could well have been errors in our code, such as the one that we
just fixed, that behave differently under the unique stress of multi-threads
(and SMP ... did I mention that my production server runs multiple
processors?) with heap profiling.  Heap profiling slows down processing
considerably, and can expose synchronization issues.

> What's the key to reproducibility?

If I knew the answer, I'd have fixed the problem.  :-)  I find this as
frustrating as you do, but I'm not going to ignore that it exists.

> You said that the traffic is not important.. I don't understand how
> you understood this.

Because I know how traffic has varied over time.  :-)

> You proposed the log rotation issue: I did a lot of tests to try
> it and demostrate we are on the bad side of our search.

So much for that hypothesis.  :-)

> What scare me is that using hprof we still don't know if we have
> to look in phoenix logs, in dnsjava, in mysql connector, or
> somewhere else..

What I need, and couldn't get the last time so I'll try it a bit
differently, is a series of heap profiles over a several day period.

        --- Noel



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to