-
Type:
Bug
-
Resolution: Answered
-
Priority:
Low
-
Affects Version/s: None
-
Component/s: None
-
Environment:
both AtlasEye and EAC/CRU
-
Severity 3 - Minor
-
1
In the logs from both AtlasEye and EAC/CRU there are warnings about ehcache initialising with the default ehcache-failsafe.xml configuration.
From the logs it isn't obvious where the warning is coming from. It is unlikely that this is coming from the FishEye caches, as errors would occur if the ehcache.xml wasn't found. Possibly a plugin is causing the problems?
WARN
net.sf.ehcache.config.ConfigurationFactory
No configuration found. Configuring ehcache from ehcache-failsafe.xml found in the classpath: bundle://21.0:1/ehcache-failsafe.xml
[2010-09-05 18:57:55,913]
WARN
org.hibernate.cache.ReadWriteCache
An item was expired by the cache while it was locked (increase your cache timeout): com.cenqua.crucible.model.Review#5270
[2010-09-06 02:41:05,962]
WARN
org.hibernate.cache.ReadWriteCache
An item was expired by the cache while it was locked (increase your cache timeout): com.cenqua.crucible.model.Review#5279
[2010-09-06 09:47:28,111]
WARN
org.hibernate.cache.ReadWriteCache
An item was expired by the cache while it was locked (increase your cache timeout): com.cenqua.crucible.model.Review#5282
[2010-09-06 11:02:13,195]
- mentioned in
-
Page Loading...