This week's book giveaway is in the Mac OS forum. We're giving away four copies of a choice of "Take Control of Upgrading to Yosemite" or "Take Control of Automating Your Mac" and have Joe Kissell on-line! See this thread for details.
I'm fairly new to creating Servlets so I'd bet the answer to this is well know but I can't seem to generate the proper search to find the answer.
My prototype is starting to actually do some useful work although I'm still at the point where my to do list is about the same size as the code base. It's a good research process to see which is growing faster.
When I stop or redeploy the next version and do a Find Leaks I get the message:
I'm developing in NetBeans. Running the NB profiler does suggest that I'm leaving classes loaded.
#1 Is there an easy way to figure out which classes are still loaded?
#2 Perhaps, I just haven't learned the proper way to exit a servlet. Any suggested reading for me?
Thanks, I really appreciate the help I've gotten from the Ranch.
It's not what your program can do, it's what your users do with the program.
I suspect it is NetBeans and the undeploy-reload cycle causing the problem.
If you run Tomcat directly - for example as an application using startup.bat - and shut it down with shutdown.bat - the JVM completely exits leaving nothing in memory so this development problem will not affect a production system.