Re: [transfer-dev] Cache Manager Shutdown problems

[Mark Mandel]

On Sun, Dec 20, 2009 at 6:18 PM, Elliott Sprehn <esp...@gmail.com> 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: mark....@gmail.com
T: http://www.twitter.com/neurotic
W: www.compoundtheory.com

[Dorioo]

Re: Memory. Something else to keep in mind as you debug:

"There’s one big deal to watch out for with this new approach. The whole idea of SoftReferences is that they will get garbage collected if they need to, like when you’re running out of memory. This default cache has no such provision. So, if you stipulate the cache can hold 10,000 objects but you only have RAM for 5,000 objects, your server is going to grind to a halt as it runs out of memory and either starts going to disk or throws java.lang.OutOfMemory errors. Either way, not good!"

http://www.ghidinelli.com/2009/11/18/using-transfer-ehcache

- Gabriel

On Sun, Dec 20, 2009 at 2:18 AM, Elliott Sprehn <esp...@gmail.com> 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.

I'm also seeing a HUGE jump in memory usage since switching to the
pluggable cache. Up to triple the memory usage.

Rolled back to pre-pluggable cache on our machines until I can figure
this one out.

Anyone else seeing this?

Going to be doing more debugging monday to see where some of the
issues are from.

--
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 transf...@googlegroups.com
To unsubscribe from this group, send email to transfer-dev...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/transfer-dev?hl=en