On Sun, Dec 20, 2009 at 6:18 PM, Elliott Sprehn <[email protected]> wrote:
> I'm seeing lots of issues with the new cache manager stuff. In > particular I'm having issues where once I shutdown the cache manager I > can never restart it. That is, even if I do structClear(application) > and create a brand new Transfer instance it still says "Cache Manager > Shutdown" every time. > Not seen this - and I run unit tests over and over... What is the exact error with stack trace? > > I'm also seeing a HUGE jump in memory usage since switching to the > pluggable cache. Up to triple the memory usage. > What is your ehcache config? It is worth noting that timetolive and timetoidle *do not* affect memory usage. They only affect the lifecycle of the objects. (There is a method to force these objects to expire if need be). These objects are only expired when they are accessed and found that they have lived too long, or have idled too long, and not before. This is different from the Transfer cache implementation. The setting that controls memory usage is maxElements - as this controls the maximum number of objects that can be stored within a cache. This is the number that must be tweaked. Mark -- E: [email protected] T: http://www.twitter.com/neurotic W: www.compoundtheory.com -- Before posting questions to the group please read: http://groups.google.com/group/transfer-dev/web/how-to-ask-support-questions-on-transfer You received this message because you are subscribed to the Google Groups "transfer-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/transfer-dev?hl=en
