Coherence CE v22.06.9
This is patch 9 of the Coherence CE 22.06 release.
New features in Coherence CE 22.06.9
COH-30158Added Listener Key Count, Listener Filter Count and Listener Registration Count to report-cache-storage.xml.COH-30148Added support to allow the definition of custom executors for the remote executor service via XML configuration.COH-30142Added support for advanced task orchestration across multiple JVMs via theRemoteExecutorAPI.COH-30058Reduced memory allocation when creating aPartitionSetinstance for a single partition, to improve memory profile of parallel queries against caches with high partition count.COH-30039The coherence-json module's POF configuration file is now auto discoverable when using POF serialization.COH-29934Added support for macro parameter expansion to<cdi:bean/>content expressionCOH-29784Improved the cleanup process of persistence files to handle case when data is deleted followed by a period with no cache activity.COH-29691ImprovedPortableTypeGeneratorto report an error when a POF annotated field is declared as final.COH-29676Improved the process of loading management-http-config.xml so that the file can be overridden by placing another management-http-config.xml file in the classpath before coherence.jar.COH-29598Improved the process of loading management-config.xml so that the file can be overridden by placing another management-config.xml file in the classpath or module path before coherence.jar.
Bugs fixed since Coherence CE 22.06.8
COH-30319Fixed an issue where the Coherence health API could report ready before all services had started.COH-30247Fixed an issue where thecoherence.distributed.partitioncountsystem property was not honored when using the default cache configuration.COH-30209Fixed an issue where rolling restart with persistence done concurrently by 2 or more nodes may result in the cache service going into theORPHANEDstate and require a cluster restart.COH-30178Fixed an issue which could prevent tasks from being executed byRemoteExecutors.COH-30157Fixed an issue where the cluster service may be stopped in very rare circumstances due to an unhandledUnsupportedOperationException.COH-30067Fixed an issue whereCacheMappingRegistry.register()orSchemeMappingRegistry.register()will throw aNullPointerExceptionif the registry is not initialized.COH-30023Fixed an issue where, in certain cases, remote invocation using anArrayFilterwould use excessive CPU.COH-30006Fixed an issue where topic subscribers could become disconnected and hang attempting to reconnect. The fix for this issue means that when using topics is it not possible to perform a rolling upgrade from versions prior to 14.1.1-2206-4. If a rolling upgrade is required it must be done in two stages, first to a version 14.1.1-2206-4 or higher then to the 14.1.1-2206-9. This rolling upgrade restriction only affects applications that are using topics.COH-29822Fixed an issue where XSD schema validation may fail in coherence-operational-config.xsd when using JDK22 or greater and setting-Djdk.xml.jdkcatalog.resolve=strict.COH-26683Fixed an issue whereMessageBuswould heartbeat at double the configured interval.COH-24703Removed an unnecessary stack trace that is logged when a member leaves a cluster.COH-23555Fixed an issue where near, view, and continuous query caches may contain stale data after snapshot recovery.
Known Issues
Due to earlier incompatibility issue with 22.06 and 22.06.1 releases, it is not possible to do a rolling upgrade directly from those releases to this patch set.
You can however do this rolling upgrade in two phases:
- 22.06 or 22.06.1 -> 22.06.2
- 22.06.2 -> current patch set
For more information on pre-requisites for performing a rolling restart, see the 14.1.1.2206 documentation