March, Andres wrote:
I have a patch for the OSCache classes that are part of hibernate to fix the issues with clustering when using this provider. If you were not aware, the cluster listener is set up in oscache per cache instance. Since the provider was creating a cache for each region, it would fail in a clustered configuration because unless you are running a supercomputer you cannot start up that many JChannels. The cache per region only allows one to specify capacity per region. Expiry policy (the real advantage of OSCache) is specified per entry.
Basically I modified the provider to create only a single cache administrator. Because of limitations in OSCache the administrator can only have 1 cache (but I plan to change this in the future). Again all we lose is the ability to specify capacity per region. OSCache does have the idea of groups which allow it to flush a region.
So the question is, do you want this patch? I already have changes I had to make to 2.1 that you guys have told me you will not integrate. So if you don’t want it I don’t really care. Just trying to help.
I'm not confident, I'll let Gavin choose about your order by improvement.
-dres.
-----------------------------------------
Andres March
Platform - Apps Engineering
Sony Online Entertainment
desk: 858.577.3373
cell: 619.519.1519
-- Emmanuel Bernard [EMAIL PROTECTED] http://www.hibernate.org
------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
