Este conteúdo não está disponível no idioma selecionado.
Chapter 3. Known and Fixed Issues
Learn about known issues in Data Grid and find out which issues are fixed.
3.1. Known Issues for Data Grid Copiar o linkLink copiado para a área de transferência!
- IllegalArgumentException when performing rolling upgrades with transactional caches
Issue: JDG-4315
Description: It is not possible to perform a rolling upgrade with transactional caches. Upgrades fail and the following exception is written to logs:
Copy to Clipboard Copied! Toggle word wrap Toggle overflow Workaround: There is no workaround for this issue.
- IOException occurs with Data Grid CLI on OpenShift
Issue: JDG-4292
Description: Running the Command Line Interface (CLI) from Data Grid pods running on OpenShift results in an
java.io.IOException: Permission denied
message.For example, if you connect to the pod using
oc rsh <pod-name>
and then invoke the CLI from the/opt/infinispan/bin
directory, when you quit the CLI the exception is thrown.This exception is related to the Aesh component and can be safely ignored.
Workaround: Download Data Grid Server and use the CLI on your local host system.
bin/cli.sh -c https://$SERVICE_HOSTNAME:11222/ --trustall
$ bin/cli.sh -c https://$SERVICE_HOSTNAME:11222/ --trustall
Copy to Clipboard Copied! Toggle word wrap Toggle overflow
- Data Grid on OpenShift continually restart after OOM exceptions
Issue: JDG-3991
Description: If out of memory exceptions cause Data Grid Server to terminate on OpenShift, the nodes cannot restart. The following exception is written to the pod log file:
FATAL (main) [org.infinispan.SERVER] ISPN080028: Red Hat Data Grid Server failed to start java.util.concurrent.ExecutionException: org.infinispan.manager.EmbeddedCacheManagerStartupException: org.infinispan.commons.CacheException: Initial state transfer timed out for cache org.infinispan.LOCKS on <pod-name-id>
FATAL (main) [org.infinispan.SERVER] ISPN080028: Red Hat Data Grid Server failed to start java.util.concurrent.ExecutionException: org.infinispan.manager.EmbeddedCacheManagerStartupException: org.infinispan.commons.CacheException: Initial state transfer timed out for cache org.infinispan.LOCKS on <pod-name-id>
Copy to Clipboard Copied! Toggle word wrap Toggle overflow Workaround: There is no workaround for this issue.
- Cannot authenticate with Data Grid Server from HotRod Store or NodeJS clients
Issue: JDG-3868
Description: If you use the HotRod store on Red Hat JBoss EAP to externalize session data to Data Grid, or if you use the Hot Rod NodeJS client, you cannot connect to Data Grid servers that require client authentication, which is the default configuration.
Workaround: Use the
remote-store
implementation with Red Hat JBoss EAP 7.3 in combination with server authentication. To use the HotRod store on Red Hat JBoss EAP, or to use Hot Rod NodeJS clients, you must disable Data Grid Server authentication.
- Inconsistent query behavior when indexed caches contain non-indexed Protobuf entities
Issue: JDG-3972
Description: If a cache is indexed but contains a Protobuf entity that is not indexed, search operations on that cache return inconsistent results.
Workaround: There is no workaround for this issue.
- Data Grid Conflict Resolution Performance
Issue: JDG-3636
Description: In some test cases, Data Grid partition handling functionality took longer than expected to perform conflict resolution.
Workaround: There is no workaround for this issue.
- Data Grid Does Not Passivate JWS Sessions Correctly
Issue: JDG-2796
Description: When externalizing sessions from JBoss Web Server (JWS), sessions are not passivated correctly if using the
FINE
persistence strategy.Workaround: There is no workaround for this issue.
3.2. Fixed in Data Grid 8.1.1 Copiar o linkLink copiado para a área de transferência!
Data Grid 8.1.1 includes the following fixes:
- JDG-4274 Rolling upgrade operations do not work with caches that store POJOs "application/x-java-objects".
- JDG-4262 Exceptions occur when iterating over embedded caches when partition handling is configured.
- JDG-4270 The metrics endpoint calls size when gathering statistics which degrades performance.
- JDG-4212 Possible deadlocks occur if an entry is replaced at the same time expiration takes effect.
- JDG-4202 Console shows a blank page when cache authorization is configured.
- JDG-3367 Hot Rod C++ client cannot be installed on Red Hat Enterprise Linux 8.
- JDG-4043 Potential race condition exists in EncoderCache.
- JDG-4062 Hot Rod C++ client behaves unexpectedly when server not running.
- JDG-4116 Data Grid Operator upgrade process fails when upgrading from 8.0.
- JDG-4162 Implicit authentication configuration overwrites custom authentication configuration.
- JDG-4177 Server garbage collection logging configuration not valid with Java 11.
- JDG-4200 REST endpoint provides incomplete chunked static resources.
- JDG-3989 Performance degradation occurs if backup locations become unavailable.
- JDG-4016 Data Grid Operator overwrites creation timestamps.
- JDG-3956 Null pointer exception occurs when accessing data during state transfer operations.
- JDG-3971 Excessive messages written to log files when writing to caches with offline backups.
- JDG-3494 Cannot Access Caches If Names Contain the "/" Character.
- JDG-3504 Remote Cache Stores Cannot Use Preload with EAP Session Externalization.
3.3. Fixed in Data Grid 8.1.0 Copiar o linkLink copiado para a área de transferência!
Data Grid 8.1.0 includes the following fixes:
- JDG-3826 Global persistent locations do not retrieve server data path property.
- JDG-3591 Data Grid Operator does not encrypt endpoints by default.
- JDG-3624 Data Grid Server allows REST and Hot Rod operations from unauthenticated users
- JDG-3799 Cache configuration exception caused by PartitionStrategy must be ALLOW_READ_WRITES when numOwners is one.
- JDG-3738 Uneven segment distributions can happen after the rebalancing with SyncConsistentHashFactory.
- JDG-3675 Logging through stdout includes colour codes.
- JDG-3586 Console creates a local cache if no configuration is provided.