It's most likely a race condition in the UtilCache getOrCreate method (the exact name escapes me without looking). Does it a actually cause any issues or is it just strange? On 20 Jan 2016 11:41, "Len Shein" <lsh...@solveda.com> wrote:
> All, > > There have been instances where one or more of the entitycache store gets > an > index number appended to it's name. > > The UtilCache.java file has the following notation: > > > > /** An index number appended to utilCacheTable names when there are > conflicts. */ > > private final static ConcurrentHashMap<String, AtomicInteger> > defaultIndices = new ConcurrentHashMap<String, AtomicInteger>(); > > > > Does anyone know what kind of conflict would cause a cache store to get > such > an index number? > > Also the original named cache is no longer present in the cache store list? > > > > For example: > > entitycache.entity.default.ProdCatalog1 > > And the original is gone. > > entitycache.entity.default.ProdCatalog > > > > Note: This is occurring in a clustered environment which we are using > ActiveMQ to distribute our cache clearing. > > > > Len Shein > > lsh...@solveda.com > > O: 516.742.7888 x225 > > O: 732.333.4303 > > C: 917.882.8515 > >
