5.2. Resolved Issues
- BZ-1378498 - ClientListener stops working after connection failure
- After a connection failure to a JDG server, normal operations like get and put recover and work as expected. But a
ClientListener
stops working. After registering the listener usingcache.addClientListener(listener)
again, it recovers and works as expected.This issue is resolved as of Red Hat JBoss Data Grid 6.6.2. - BZ-1382273 - NPE in CacheNotifierImpl by LIRS eviction listener
- When inserting 20 key/values in a 10 sized cache (keys from key-1 to key-20) and then reinserting the first 10 keys (key-1 to key-10) while also using LIRS eviction strategy and listener, a
NullPointerException
is thrown inCacheNotifierImpl.notifyCacheEntriesEvicted
. This issue existed in both Remote Client-Server mode and Library mode.This issue is resolved as of Red Hat JBoss Data Grid 6.6.2 - BZ-1383945 - Expiration is not working under some circumstances with AtomicMap
- Previously, when using AtomicMaps and writeskew, lifespan as set in the configuration wasn't applied. This has been addressed in JBoss Data Grid 6.6.2 and now lifespan in the configuration is honored.
- BZ-1388562 - Expiration is not applied to a repeatable read entry that was read as null prior
- The expiration metadata is not applied to a newly created entry that was read in the same transaction as a null.This issue is resolved as of Red Hat JBoss Data Grid 6.6.2.
- BZ-1379414 - @CacheEntryExpired not getting invoked for non auto-commit cache
@CacheEntryExpired
listener method is not invoked for non auto-commit cache. When auto commit is true the listener method is invoked.@CacheEntryCreated
is invoked in both configs.This issue is resolved as of Red Hat JBoss Data Grid 6.6.2.- BZ-1412752 - MissingFormatArgumentException thrown by PreferConsistencyStrategy if debug mode is enabled on state-transfer or merge
- Methods
PreferConsistencyStrategy
andStateConsumerImpl
contained non-typesafe printf errors.This issue is resolved as of Red Hat JBoss Data Grid 6.6.2. - BZ-1428027 - DMR operation register-proto-schemas fails with NPE if the proto file has syntax errors
- If the proto file has syntax errors it isn't placed in the
___protobuf_metadata
cache as it should be. Additionally, amyFileWithSyntaxErrors.proto.errors
key fails to be created and an exception is thrown.This issue is resolved as of Red Hat JBoss Data Grid 6.6.2. - BZ-1431965- SimpleDateFormat used in REST server is not thread safe
org.infinispan.rest.Server
has a static field ofDatePatternRfc1123LocaleUS
, wihich is an instance ofSimpleDateFormat
. This causes ajava.lang.ArrayIndexOutOfBoundsException
under load.This issue is resolved as of Red Hat JBoss Data Grid 6.6.2.- BZ-1425687 - JDG client unable to resolve the system property in external-host jdg6
- If
infinispan.external_addr
is defined in a server configuration file likeclustered.xml
, the JBoss Data Grid client will be unable to resolve the address.This issue is resolved as of Red Hat JBoss Data Grid 6.6.2. - BZ-1440102 - Cache clear doesn't work when passivation is enabled
- Clearing the cache map doesn't work under the following configuration: JBoss Data Grid is running in Library mode inside JBoss EAP 6.4.6 with passivation enabled. In this case the size will never be reduced to 0.This issue is resolved as of Red Hat JBoss Data Grid 6.6.2.
- BZ-1388888 - LIRS Eviction with local cache under high load fail with a NullPointerException at BoundedEquivalentConcurrentHashMapV8.java:1414
- When using
LIRSEvictionPolicy
in some situations aNullPointerException
can occur inBoundedEquivalentConcurrentHashMapV8
. The error is harmless but the issue has been fixed.This issue is resolved as of Red Hat JBoss Data Grid 6.6.2. - BZ-1448366 - HotRod client write buffer is too large
- The Hot Rod client uses more memory than it should. The buffering implementation of
TcpTransport.socketOutputStream
does not use a fixed sized input buffer. Instead it grows asBufferedInputStream
does. A growing buffer can lead to excessive memory consumption in the heap, as well as in the native memory of the operating system.This issue is resolved as of Red Hat JBoss Data Grid 6.6.2. - BZ-1435617 - Rolling upgrade fails with java.lang.ClassCastException
- Previously, performing a rolling upgrade could fail with a
java.lang.ClassCastException
of eitherorg.infinispan.container.entries.RepeatableReadEntry cannot be cast to org.infinispan.container.entries.InternalCacheEntry
orSimpleClusteredVersion cannot be cast to NumericVersion
.This issue is resolved as of Red Hat JBoss Data Grid 6.6.2. - BZ-1435618 - Hot Rod Rolling Upgrade throws TimeOutException
- When doing a rolling upgrade that takes more than a few minutes to complete a
TimeOutException
could be thrown.This issue is resolved as of Red Hat JBoss Data Grid 6.6.2. - BZ-1435620 - Rolling Upgrade: use of Remote Store in mode read-only causes data inconsistencies
- Previously, during Hot Rod rolling upgrades, write operations executed by the client on the target cluster were ignored. This could cause unexpected results in the application, such as entries being deleted that weren't intentionally deleted.This issue is resolved as of Red Hat JBoss Data Grid 6.6.2.