[Building Sakai] has anyone seen one of these before? hibernate cache death.

[Jim Eng]

Ian:  This is reaching back to ancient times for you, I'm sure, but you gave
the following advice five years ago.  I'm not sure I understand correctly,
but it seems like the second paragraph may be saying that a hibernate jar is
being deployed in some sakai component war instead of having that component
rely on a common hibernate jar.  If that's the case, would it make sense to
try to find the culprit by looking for a hibernate jar in a component war
and then revising the poms for that project to avoid including the hibernate
jar in the war? Would it make sense to think the cause of this must be a
contrib or local project rather than part of sakai's kernel or core because
otherwise it would be a common problem?



Ian Boston-2 wrote:
> 
> This is caused the ehcache singleton being bound to in a war and that 
> war being reloaded.
> 
> Its often caused by having a Hibernate Session factory inside the war 
> rather than in components or a secondary use of ehcache.
> 
> The really nasty thing about this, is that you may not get the error 
> message until some point after the suspect war has reloaded as it 
> doesn't happen until one of the consumers of ehcache tries to access a 
> stale copy of ehcache.
> 

-- 
View this message in context: http://old.nabble.com/has-anyone-seen-one-of-these-before--hibernate-cache-death.-tp9054857p34779895.html
Sent from the Sakai - Development mailing list archive at Nabble.com.