There is no guarantee for an answer here as it is a user group list...and nobody will waste his own time for problems of unkind peoples...
Call stopService(), followed by destroyService()
I noticed a bunch of your posts going to our STAGING focum server - I have no idea how you got a link to this, but this explains why no one was notified of the entry.
I would suggest bookmarking http://www.jboss.com/index.html?module=bb&op=viewforum&f=157 as the JBossCache forum page! :-)
Anyway, this question was one that I did actually spot on the staging server, and even respond to (but again, on the staging server) and hence my request to you to re-post on this server.
My original response:
destroying the service will not help you. Resources are all released when you call stopService().
Do you assign the cache variable to null when you are done with it?
Oh, and JBoss engineers respond to this list too; not just users! ;)
Okay ... I am stopping the cache service but its must be leaving some references open somewhere...as previously stated I have interfaced out the caching in my applications so if I swap the cache for a simple hashmap implementation then I don't get the memory problems.
hotdeploying my service over and over again eventually gives errors when using the jboss cache.
Like I said,when you stop the cache, do you also remove the reference to your TreeCache object?
I am creating the cache as part of my service and what I am doing is hot deploying my .sar file so any references to the cache should be discarded anyway since the objects that hold the cache reference are instances of the packages in the sar file so I am guessing that unloading and reloading the service should clear down the references.
Does the classloading in Jboss work in this way?