Hello Jeff,
Why not just analyse the heap dump with jhat or a profiler? That's the normal
approach for investigating an OOME and you should be able to see very quickly
what's using all the memory. There's usually little need to try and speculate
about the problem like this or manually eyeball your code.
Midway through the development of a new app, our
Integration/Functional tests began failing with OOM. -Xmx is set to
1024m, so there should be plenty of memory. Our Logback test
configuration logs to console, text file, and Lilith file.
_______________________________________________
Logback-user mailing list
[email protected]
http://qos.ch/mailman/listinfo/logback-user
