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. -dres. ----------------------------------------- Andres March Platform - Apps Engineering Sony Online Entertainment desk: 858.577.3373 cell: 619.519.1519 |
- [Hibernate] Fix for OSCache clustering March, Andres
- Re: [Hibernate] Fix for OSCache clustering Emmanuel Bernard
- Re: [Hibernate] Fix for OSCache clustering Gavin King
- RE: [Hibernate] Fix for OSCache clustering March, Andres