Hibernate 异常CacheException: Another unnamed CacheManager already exists in the same VM
2017-05-01 21:04
411 查看
原因：
ehcache在2.5以后，CacheManager使用了Singleton，这样在创建多个CacheManager时就会产生上述错误。
解决方法：
把
改成
ehcache在2.5以后，CacheManager使用了Singleton，这样在创建多个CacheManager时就会产生上述错误。
解决方法：
把
<property name="hibernate.cache.region.factory_class">org.hibernate.cache.ehcache.EhCacheRegionFactory</property>
改成
<property name="hibernate.cache.region.factory_class">org.hibernate.cache.SingletonEhCacheRegionFactory </property>
内容来自用户分享和网络整理，不保证内容的准确性，如有侵权内容，可联系管理员处理 
相关文章推荐
- hibernate3与ehcache-2.8.3配合使用，在多个SessionFactory实例的情况下出现“Another unnamed CacheManager already exists in the same VM”问题
- Ehcache配置时出错- Another unnamed CacheManager already exists in the same VM. Please provide unique name
- Another unnamed CacheManager already exists in the same VM.解决方法
- Another unnamed CacheManager already exists in the same VM
- SpringBoot--P-1：缓存 Another unnamed CacheManager already exists in the same VM.
- net.sf.ehcache.CacheException: Another unnamed CacheManager already exists in the same VM.
- Another unnamed CacheManager already exists in the same VM
- net.sf.ehcache.CacheException: Another unnamedCacheManager already exists in the same VM
- Another unnamed CacheManager already exists in the same VM (ehCache 2.5) 解决办法
- 在整合springmvc+mybatis+ecache时候报错如下： Another unnamed CacheManager already exists in the same VM.
- Another unnamed CacheManager already exists in the same VM.解决方法
- Another unnamed CacheManager already exists in the same VM
- Ehcache依赖版本问题：Another CacheManager with same name 'es' already exists in the same VM.
- Excel导入遇到的问题An object with the same key already exists in the ObjectStateManager……
- Socket file /tmp/mysql.sock exists. Is another MySQL daemon already running with the same unix socke
- ehcache2.5后hibernate多SessionFactory报错的解决(Another unnamed CacheManager )
- Socket file /var/lib/mysql/mysql.sock exists. Is another MySQL daemon already running with the same
- SVN Folder already exists in therepositor解决
- SQL2000: Error 15023: User or role '%s' already exists in the current database
- This generally means that another instance of this process was already running or is hung in the deb