Chapter 6. Resolved Issues

When enabling security on a cache, cross-site replication did not work.

This issue is resolved as of JBoss Data Grid 7.1.

When creating a new template the JDBC cache store configuration was not copied over, and must have been manually entered instead.

This issue is resolved as of JBoss Data Grid 7.1.

Unlike the C++ and Java Hot Rod clients, the C# client did not include asynchronous versions of cache operations.

The asynchronous versions of cache operations have been included, and this issue is resolved as of JBoss Data Grid 7.1.

When updating one server group’s transport configuration through the Administration Console, and accepting the prompt to restart, the server group remained running. Instead, a second server group was restarted in its place.

This issue is resolved as of JBoss Data Grid 7.1.

When examining the port for containers in the Administration Console the port-offset was not considered, causing multiple containers to show at the same port.

This issue is resolved as of JBoss Data Grid 7.1.

When attempting to use the JGroups ENCRYPT protocol an ArrayIndexOutOfBoundsException was thrown.

This issue is resolved as of JBoss Data Grid 7.1.

When using putAll() or getAll() during a topology change there was the possibility for data being lost, resulting in fewer entries placed or retrieved than expected.

This issue is resolved as of JBoss Data Grid 7.1.

When attempting to store entries in MS SQL 2012 or 2008R2 servers, any string-based cache store would fail if the data was stored using a Hot Rod client, as these SQL servers did not support UTF-8 encoding.

This issue is resolved as of JBoss Data Grid 7.1.

When attempting to use TLS authentication on Windows 7 no connection could be made to the server. Instead, the connection attempt would error out with the following message:

**** Error 0x80092004 returned by CertCreateCertificateContext. Cannot create certificate. File corrupted?

This issue is resolved as of JBoss Data Grid 7.1.

The version of the Hot Rod Node.js client was infinispan-0.4.0-redhat-SNAPSHOT, instead of the 0.3.0-ER6-redhat-1 expected by the hotrod-endpoint-js quickstart.

This issue is resolved as of JBoss Data Grid 7.1.

When attempting to use TLS authentication on Windows, the server was unable to read certificates through the filesystem.

This issue is resolved as of JBoss Data Grid 7.1.

When attempting to access the Administration Console in standalone mode, using the standalone.xml configuration file, errors were repeatedly thrown.

This issue is resolved as of JBoss Data Grid 7.1.

When performing a rolling upgrade the remote-store was placed into read-only mode, resulting in issues if applications expected consistent access to data during the rolling upgrade process.

This issue is resolved as of JBoss Data Grid 7.1.

When performing a rolling upgrade a ClassCastException was thrown.

This issue is resolved as of JBoss Data Grid 7.1.

When performing a rolling upgrade from JBoss Data Grid 6.6.1 to JBoss Data Grid 7.x, remote iteration was not used as it required a Hot Rod protocol version of 2.5, even though JBoss Data Grid 6.6.1 supports remote iteration.

This issue is resolved as of JBoss Data Grid 7.1.

The org.infinispan.rest.Server class has an instance of SimpleDateFormat, which resulted in errors during concurrent access.

This issue is resolved as of JBoss Data Grid 7.1, as the instance has been adjusted to DateTimeFormatter.

When attempting to implement security on the REST interface in JBoss Data Grid 7.0 the settings were ignored, allowing clients to access this interface without providing the required credentials.

This issue is resolved as of JBoss Data Grid 7.1.