Chapter 6. Resolved Issues

In distributed cache mode with L1 enabled and onRehash=true, when an entry was overwritten during state transfer, the overwrite was often ignored. This node would then report an outdated value of the entry, and after the L1 timeout, the entry was completely removed.

This issue is now resolved in JBoss Data Grid 6.3.0.

In the JBoss Data Grid Library and JBoss Operations Network integration, the default 5000 millisecond timeout period for an availability check operation was not sufficient to monitor an application that used JBoss Data Grid libraries deployed on a JBoss EAP server. As a result, the availability of the embedded Infinispan cache manager was inaccurately reported as alternating between UP and DOWN. Additionally, the monitoring of cache statistics was affected by this issue.

This issue is now resolved in JBoss Data Grid 6.3.0.

The Red Hat JBoss Data Grid server plug-in for JBoss Operations Network did not cover a full set of management operations. Therefore, a subset of management operations was not accessible from the JBoss Operations Network user interface.

This issue is now resolved in JBoss Data Grid 6.3.0.

The org.infinispan.client.hotrod.impl.transport.tcp.RequestBalancingStrategy interface has changed although it is considered part of public API. If the application using JBoss Data Grid directly uses (implements) this interface, upgrading to JBoss Data Grid 6.3 was not possible without changing the application code.

This issue is now resolved in JBoss Data Grid 6.3.0.

A Hot Rod client running in Karaf could not store or retrieve user-defined objects. This was because custom classes were packaged in the client's bundle and the Hot Rod client could not see these classes.

This issue is now resolved in JBoss Data Grid 6.3.0.

The Hot Rod Java client configuration validator did not accept a configuration where the SASL callback handler was not set. However, if a valid client Subject is supplied instead, the validator accepts the configuration. As a result, the configuration validator threw a org.infinispan.commons.CacheConfigurationException exception with the following error message:

This issue is now resolved in JBoss Data Grid 6.3.0.

If JPA Cache Stores were used with the metadata storage attribute disabled, the cache store executed the queries for the metadata when other operations occured. As a result, if the metadata class was disabled in the persistence.xml file, other operations failed to execute or did not perform optimally.

This issue is now resolved in JBoss Data Grid 6.3.0.

The native LevelDB JNI library used by the LevelDB store was built using the C++ compiler available in Red Hat Enterprise Linux 6, which made the resulting binary ABI-incompatible with Red Hat Enterprise Linux 5. As a result, the LevelDB JNI library failed to load with a linker error reporting a missing version symbol (/usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.9' not found).

This issue is now resolved in JBoss Data Grid 6.3.0.

When the LevelDB expire queue filled up, the queue-size parameter was not parsed. As a result, write operations were blocked because the queue is considered full.

This issue is now resolved in JBoss Data Grid 6.3.0. The parser has been fixed and it is now possible to configure the queue-size.