Chapter 9. Updates and Enhancements in 7.3.3

9.1. Data Grid Server Upgraded to JBoss Enterprise Application Platform (EAP) 7.2.4

Data Grid server is upgraded to EAP 7.2.4, which provides performance improvements and includes several CVE fixes to enhance security.

Changes to the AWS S3 API require Data Grid to use NATIVE_S3_PING instead of the JGroups S3_PING protocol.

JGroups S3_PING no longer works for server discovery on AWS. You should migrate any existing S3_PING configurations to NATIVE_S3_PING.

For more information, see the following:

This release includes changes that improve transport layer performance for Data Grid clusters in Library Mode:

Data Grid adds JGroups Unicast Flow Control (UFC) to default TCP transport stacks. UFC prevents nodes from sending asynchronous messages to other nodes when the JGroups thread pool for the receiving nodes reaches maximum capacity. When this occurs, receiving nodes start discarding messages but sending nodes keep re-sending them.
The value for the max_credits attribute for UFC and MFC increases to 3m from the JGroups default of 2m. This attribute sets the maximum number of bytes that one node can send to another without an acknowledgment from the receiving node.

Note

UFC is already included in the default UDP transport stack for Library Mode.
In Server Mode, Data Grid uses non-blocking flow control (UFC_NB and MFC_NB) as default.

The Data Grid REST endpoint now allows access to caches that are configured for authorization.

This enhancement resolves the issues outlined in this KCS Solution.

The protostream library component in Data Grid is updated to 4.2.4.Final.