Does anyone know if two applications deployed with two versions of Hibernate co exist together? I am getting the following error when an application that uses Hibernate 3.0 is deployed to the application server .

Please let me know the solution to avoid this.

Cache is not alive.
at net.sf.ehcache.Cache.checkStatus(Cache.java:437)
at net.sf.ehcache.Cache.get(Cache.java:217)
at net.sf.ehcache.hibernate.Plugin.get(Plugin.java:119)
at net.sf.hibernate.cache.ReadOnlyCache.get(ReadOnlyCache.java:26)
at net.sf.hibernate.impl.SessionImpl.doLoad(SessionImpl.java:2105)
at net.sf.hibernate.impl.SessionImpl.doLoadByClass(SessionImpl.java:1988)
at net.sf.hibernate.impl.SessionImpl.internalLoad(SessionImpl.java:1950)
at net.sf.hibernate.type.ManyToOneType.resolveIdentifier(ManyToOneType.java:69)
at net.sf.hibernate.type.EntityType.resolveIdentifier(EntityType.java:204)
at net.sf.hibernate.impl.SessionImpl.initializeEntity(SessionImpl.java:2202)
at net.sf.hibernate.loader.Loader.doQuery(Loader.java:240)
at net.sf.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:133)
at net.sf.hibernate.loader.Loader.doList(Loader.java:955)
at net.sf.hibernate.loader.Loader.list(Loader.java:946)
at net.sf.hibernate.hql.QueryTranslator.list(QueryTranslator.java:846)
at net.sf.hibernate.impl.SessionImpl.find(SessionImpl.java:1544)
at net.sf.hibernate.impl.QueryImpl.list(QueryImpl.java:39)
at com.hfa.common.service.UserService.getUserByLogin(Unknown Source)
at com.hfa.security.authentication.AS400UserRegistry.checkPassword(Unknown Source)
at com.ibm.ws.security.registry.UserRegistryImpl.checkPassword(UserRegistryImpl.java:275)
at com.ibm.ws.security.ltpa.LTPAServerObject.authenticate(LTPAServerObject.java:384)
at com.ibm.ws.security.server.lm.ltpaLoginModule.login(ltpaLoginModule.java:291)
at com.ibm.ws.security.common.auth.module.proxy.WSLoginModuleProxy.login(WSLoginModuleProxy.java:122)
at sun.reflect.GeneratedMethodAccessor233.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:41)
at java.lang.reflect.Method.invoke(Method.java:386)
at javax.security.auth.login.LoginContext.invoke(LoginContext.java:698)
at javax.security.auth.login.LoginContext.access$000(LoginContext.java:150)
at javax.security.auth.login.LoginContext$4.run(LoginContext.java:633)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.login.LoginContext.invokeModule(LoginContext.java:630)
at javax.security.auth.login.LoginContext.login(LoginContext.java:556)
at com.ibm.ws.security.auth.JaasLoginHelper.jaas_login(JaasLoginHelper.java:250)
at com.ibm.ws.security.auth.JaasLoginHelper.jaas_login(JaasLoginHelper.java:277)
at com.ibm.ws.security.auth.ContextManagerImpl.login(ContextManagerImpl.java:801)
at com.ibm.ws.security.auth.ContextManagerImpl.login(ContextManagerImpl.java:665)
at com.ibm.ws.security.auth.ContextManagerImpl.getServerSubject(ContextManagerImpl.java:1147)
at com.ibm.ws.security.auth.ContextManagerImpl.getServerCredential(ContextManagerImpl.java:1197)
at com.ibm.ISecurityLocalObjectBaseL13Impl.VaultImpl.getServerCred(VaultImpl.java:2622)
at com.ibm.ISecurityLocalObjectBaseL13Impl.CredentialsImpl.is_cache_expiration_valid(CredentialsImpl.java:1949)
at com.ibm.ISecurityLocalObjectBaseL13Impl.VaultImpl.run(VaultImpl.java:3575)
at java.lang.Thread.run(Thread.java:568)
.

Seems like they are both getting the same underlying instance of the EHCache CacheManager.

Not really sure if that's the intended behaviour of EHCache's CacheManager.create() method (which is what both H2 and H3 use to get a CacheManager instance).