Sep 6th, 2010, 02:11 AM
detecting memory leaks2 or maybe not a leak
For the original thread, refer here:
So today, I cleaned up the application. It is no longer using the commons logger but log4j and slf4j. I also removed the spring java script and related servlet. I did this because spring.js and dojo versions do not necesarely match.. So picked one dojo js .. moving to spring js in the future.
I removed most libraries and I upgraded quartz to 1.8.3 Still, all the classloaders are very big in memory. Okay.. it is not dramatic (25 Mb ramp up.. but still) The aspectJ thing is still there. I do not know why there is all these classloaders.
Using tomcat instead of TC server, there is a drop in memory usage but... still some of this still exists. Any ideas?
I do have a singleton class that has a static dictionary of strings.. (keeping state) But that only gets populated by one string value once. I was under the impression that I was able to keep state that way.
I might be wrong that there is something going on. Did not mean to be sticky.. Still 25 Mb is quite a bit when hosting an app remotely.
Last edited by archon777; Sep 6th, 2010 at 03:42 AM.