Strange memory leak when reading serialized data in Tomcat web app?

Memory leaks are significant to Tomcat and all app servers because they're intended to stay alive for a long time. Memory leaks are an issue only if they show up over a longer period of time. Your instincts are good, but your procedures are flawed in my opinion.

I'd recommend that you use a better tool - the Visual VM that's bundled with JDK 6 and higher - and that you monitor your Tomcat while it's being used in a manner that's closer to your real production needs. You can't draw any conclusion regarding memory leaks from a single request.

1 Read in only once. And this isn't for a enterprise app- just something I'm putting together for personal use. It's not a matter of how significant the leak is, I just want to know why Tomcat is complaining.Is it a bug in Tomcat, or am I actually doing something in a "bad" way?

By the way- I rewrote the serialization to use JSON as the underlying format (using Jackson for serializing/deserializing) and Tomcat still reports a leak. Also- when I say "check for memory leaks" I'm talking about using Tomcat's own "find leaks" button in the Manager app. – user190758 Mar 14 at 2:08 Scratch that- Jackson doesn't have the problem.

Maybe Java's object serialization is doing something internally that's ill-advised? – user190758 Mar 14 at 2:20.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.