-
Bug
-
Resolution: Done
-
Major
-
7.3.3.GA
-
False
-
False
-
-
-
-
-
-
+
-
Undefined
-
When enabling query cache for a JPA persistence unit (hibernate.cache.use_query_cache=true in the persistence.xml), an unusual message is seen on the console/in the server.log:
... INFO [org.infinispan.expiration.impl.ExpirationManagerImpl] (ServerService Thread Pool -- 81) ISPN000025: wakeUpInterval is <= 0, not starting expired purge thread
This appears to indicate an error (or warning) that something is incorrect but the default cache settings (in standalone*.xml have been used). The ISPN000025 appears to be related to the configuration of the timestamps cache (based on the timing of cache start events, etc.).
If this is not an error or warning, it should be logged at DEBUG or TRACE level.
- is caused by
-
WFLY-13764 Hibernate 2LC uses wrong default cache configuration for timestamps regions
- Closed
- is related to
-
JBEAP-21048 Clustering: java.lang.ref.Reference.waitForReferencePendingList in failover tests
- Closed
- links to