GridGain 8.7.39 Release Notes

You can now use the new Compute::ExecuteJavaTask method to execute Java compute tasks from C++ code by their names. For example:

Compute tasks can now be performed by using C++ thin clients. For example, here is how you can execute a newly added compute task on :

When working with Hibernate L2, you may want to use the same cache configuration for multiple caches. Now you can use preconfigured Cache Templates to apply the same configuration to multiple caches.

For example, the following configuration uses a single transactional-cache bean for multiple entities:

When the amount of data stored on disk is bigger than the off-heap memory amount allocated for the data region, another page should be removed from off-heap to the disk to preload an appropriate page to off-heap memory.

There are three available algorithms:

By default, CLOCK algorithm is used.

Page replacement algorithm is configured by the PageReplacementMode property of DataRegionConfiguration.

If you are upgrading from version 8.7.20 or earlier, consider an incompatibility issue related to Jetty configuration introduced in GridGain 8.7.21.

Your setup may be affected if:

In this case, after starting a new version, an exception is thrown with an error message similar to the following:

To workaround this issue, alter the Jetty configuration to use org.eclipse.jetty.util.ssl.SslContextFactory$Server or org.eclipse.jetty.util.ssl.SslContextFactory$Client. See the configuration example at the Client Certificate Authentication page.

In GridGain 8.7.26, the default value of the property IgniteConfiguration.rebalanceThreadPoolSize changed from 1 to min(4, number of CPU / 4). It may cause a compatibility issue under the following conditions:

In this case, an exception is thrown with an error message similar to the following:

To workaround this issue, change the configuration of the server nodes to rebalanceThreadPoolSize=1 so that it matches the previous default configuration. For example:

In GridGain 8.7.31 Jetty was upgraded to 9.4.33. Starting that version, Jetty has more strict validation of the provided configuration files. Before that version, an incorrectly spelled property in the configuration file had no effect. Starting this version, errors in the configuration will lead to an error on start.

Your setup may be affected if:

You will need to fix the custom Jetty configuration before upgrading.

Starting from 8.7.31 version, GridGain no longer attempts to automatically enable the remote JMX. Default settings are known to cause issues if customized (for example, secure the connection). Also, in most cases, remote JMX is not required since many tools use local JMX connections (not using TCP).

Your setup may be affected if:

To continue using remote JMX, you need to manually specify the required JMX settings. Please see the example below. Note that you don’t need remote JMX if you use a local connection, such as connecting JConsole to a GridGain process on the same host.