org.hibernate.cache.ehcache.EhCacheMessageLogger.i18n.properties Maven / Gradle / Ivy

Go to download
Show more of this group Show more artifacts with this name
Show all versions of hibernate-ehcache
Integration for Ehcache into Hibernate as a second-level caching service
There is a newer version: 6.0.0.Alpha7
#####################################################################################################
#
# This file is for reference only, changes have no effect on the generated interface implementations.
#
#####################################################################################################

# Id: 20001
# Level: org.jboss.logging.Logger.Level.WARN
# Message: Attempt to restart an already started EhCacheRegionFactory.  Use sessionFactory.close() between repeated calls to buildSessionFactory. Using previously created EhCacheRegionFactory. If this behaviour is required, consider using org.hibernate.cache.ehcache.SingletonEhCacheRegionFactory.
attemptToRestartAlreadyStartedEhCacheProvider=Attempt to restart an already started EhCacheRegionFactory.  Use sessionFactory.close() between repeated calls to buildSessionFactory. Using previously created EhCacheRegionFactory. If this behaviour is required, consider using org.hibernate.cache.ehcache.SingletonEhCacheRegionFactory.
# Id: 20002
# Level: org.jboss.logging.Logger.Level.WARN
# Message: Could not find configuration [%s]; using defaults.
# @param 1: name - The name of the configuration file
unableToFindConfiguration=Could not find configuration [%s]; using defaults.
# Id: 20003
# Level: org.jboss.logging.Logger.Level.WARN
# Message: Could not find a specific ehcache configuration for cache named [%s]; using defaults.
# @param 1: name - The name of the cache configuration
unableToFindEhCacheConfiguration=Could not find a specific ehcache configuration for cache named [%s]; using defaults.
# Id: 20004
# Level: org.jboss.logging.Logger.Level.WARN
# Message: A configurationResourceName was set to %s but the resource could not be loaded from the classpath. Ehcache will configure itself using defaults.
# @param 1: configurationResourceName - The resource name we attempted to resolve
unableToLoadConfiguration=A configurationResourceName was set to %s but the resource could not be loaded from the classpath. Ehcache will configure itself using defaults.
# Id: 20005
# Level: org.jboss.logging.Logger.Level.WARN
# Message: The default cache value mode for this Ehcache configuration is "identity". This is incompatible with clustered Hibernate caching - the value mode has therefore been switched to "serialization"
incompatibleCacheValueMode=The default cache value mode for this Ehcache configuration is "identity". This is incompatible with clustered Hibernate caching - the value mode has therefore been switched to "serialization"
# Id: 20006
# Level: org.jboss.logging.Logger.Level.WARN
# Message: The value mode for the cache[%s] is "identity". This is incompatible with clustered Hibernate caching - the value mode has therefore been switched to "serialization"
# @param 1: cacheName - The name of the cache whose config attempted to specify value mode.
incompatibleCacheValueModePerCache=The value mode for the cache[%s] is "identity". This is incompatible with clustered Hibernate caching - the value mode has therefore been switched to "serialization"
# Id: 20007
# Level: org.jboss.logging.Logger.Level.WARN
# Message: read-only cache configured for mutable entity [%s]
# @param 1: entityName - The name of the entity
readOnlyCacheConfiguredForMutableEntity=read-only cache configured for mutable entity [%s]
# Id: 20008
# Level: org.jboss.logging.Logger.Level.WARN
# Message: Cache[%s] Key[%s] Lockable[%s]
A soft-locked cache entry was expired by the underlying Ehcache. If this happens regularly you should consider increasing the cache timeouts and/or capacity limits
# @param 1: regionName - The region name
# @param 2: key - The cache key
# @param 3: lock - The lock
softLockedCacheExpired=Cache[%s] Key[%s] Lockable[%s]
A soft-locked cache entry was expired by the underlying Ehcache. If this happens regularly you should consider increasing the cache timeouts and/or capacity limits