[jboss-dev] Re: Default jbosscache usage in JBoss AS 4.2/EJB3

[Carlo de Wolf]

Hmm, we did a discussion on this a while back. But then it was more
about cache start/stop semantics. Does anybody recall the subject line,
so I can find it?

Carlo

On Tue, 2007-04-17 at 10:32 -0400, Emmanuel Bernard wrote:
> Don't know who exactly, but definitely, Carlo should be aware of that.
> 
> On 17 avr. 07, at 09:57, Max Rydahl Andersen wrote:
> 
> > Hi guys,
> >
> > From various discussions I understand that JBoss AS 4.2 currently  
> > deploys a single JBC instance for use as a shared cache across EJB3  
> > deployments
> > and that individual EJB3 deployments will by default share the same  
> > cache resulting in them sharing the same cache regions.
> >
> > That is bad!
> >
> > Two independent applications should not share the same cache  
> > regions - they should *always* be seperated by setting  
> > hibernate.cache_region.prefix so
> > they only get access to the data that is actually relevant for them.
> >
> > There will also be classloading issues with such a scheme.
> >
> > From my understanding the place to fix this is in the ejb3 deployer  
> > to use whatever unique name these deployments have so the same  
> > cache_region.prefix
> > will be set correctly across different nodes etc.
> >
> > If the above assumption about 4.2 is correct, who is the right  
> > person to fix that ?
> >
> > -- 
> > --
> > Max Rydahl Andersen
> > callto://max.rydahl.andersen
> >
> > Hibernate
> > max at hibernate.org
> > http://hibernate.org
> >
> > JBoss a division of Red Hat
> > max.andersen at jboss.com
>