Chapter 2. Known and fixed issues Learn about known issues in Data Grid and find out which issues are fixed. 2.1. Known Issues for Data Grid For issues that affect Data Grid clusters that you manage with Data Grid Operator, you should refer to the Data Grid Operator 8.5 release notes . JGroups address defaults to an external IP Issue: JDG-6053 Description: In bare metal deployments, when JGroups bind to an external IP without authentication configured by default, the connection is not secure, posing a risk of unauthorized access or manipulation. Workaround: Secure the connection in one of the following ways: Configure JGroups security to control the network so only authorized nodes can join. For more information see, Encrypting cluster transport . Use the -Djgroups.bind.address=<internal-network> parameter when starting Data Grid Server to set the JGroups address to secure internal network. Inconsistent transactions when network partitions occur Issue: JDG-3935 Description: In scenarios where a network partition occurs for a Data Grid cluster, transactions are rolled back after the partition is healed. 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. 2.2. Fixed in Data Grid 8.5.2 See Issues fixed in Red Hat Data Grid 8.5.2 to view the list of issues fixed in this release. 2.3. Fixed in Data Grid 8.5.1 See Issues fixed in Red Hat Data Grid 8.5.1 to view the list of issues fixed in this release. 2.4. Fixed in Data Grid 8.5.0 Data Grid 8.5.0 includes the following notable fixes: JDG-6918 View change during a cache join can lead to not replicating data JDG-6463 Elements in collections are not properly limited JDG-7061 Concrete config is validated before applying template configuration JDG-7095 Cross site view change event logs stale view. JDG-6986 Fix out-of-order query request serialization JDG-6431 Cache local address on demand 2.5. Host system and dependency issues In some cases Data Grid deployments can encounter errors that are caused by the host system or external dependency. This section provides details about any such known issues as well as troubleshooting and workaround procedures. Nashorn JavaScript engine If your Data Grid Server uses JavaScript to automate tasks, you must install the Nashorn JavaScript engine to ensure that these scripts can run on Data Grid 8.4. This is because OpenJDK 17 has removed support for the Nashorn JavaScript engine, its APIs, and the jjs tool. For a bare-metal Data Grid Server, you can install Nashorn from the Maven central repository by issuing the following command in your Data Grid CLI: bin/cli.sh install org.openjdk.nashorn:nashorn-core:15.4 \ org.ow2.asm:asm:7.3.1 \ org.ow2.asm:asm-util:7.3.1 On OpenShift, you can create an Infinispan Custom Resource (CR) that sets the Data Grid Operator to install Nashorn for your Data Grid cluster. For example: apiVersion: infinispan.org/v1 kind: Infinispan metadata: name: infinispan spec: replicas: 2 dependencies: artifacts: - maven: org.openjdk.nashorn:nashorn-core:15.4 - maven: org.ow2.asm:asm:7.3.1 - maven: org.ow2.asm:asm-util:7.3.1 service: type: DataGrid

Commands:
bin/cli.sh install org.openjdk.nashorn:nashorn-core:15.4 org.ow2.asm:asm:7.3.1 org.ow2.asm:asm-util:7.3.1
apiVersion: infinispan.org/v1 kind: Infinispan metadata: name: infinispan spec: replicas: 2 dependencies: artifacts: - maven: org.openjdk.nashorn:nashorn-core:15.4 - maven: org.ow2.asm:asm:7.3.1 - maven: org.ow2.asm:asm-util:7.3.1 service: type: DataGrid