Coherence CE v14.1.2-0-9

This is patch 9 of the Coherence CE v14.1.2-0-0 release.

Dependency Updates (3rd‑party)

none

New features in Coherence CE v14.1.2-0-9

1. Security fixes and enhancements
2. COH-33808 Coherence Extend TCP proxies now process independent client connections through connection-affine pipelines instead of serializing all request decoding on a single acceptor thread. Each connection retains strict request ordering, while multiple connections are decoded concurrently, substantially improving proxy throughput and latency under load. Pipeline concurrency is selected automatically based on available processors and can be overridden using the new TCP acceptor setting.
3. COH-33807 Platform daemon pools now adapt worker concurrency to workload behavior. CPU-bound services remain near the available processor count, while blocking and I/O-bound services can grow beyond it when measured throughput demonstrates a benefit. Ineffective growth is automatically reversed, improving throughput and latency under blocking workloads without adding unnecessary workers to CPU-bound services.
4. COH-33801 Improved Coherence*Extend client performance by increasing the default TCP initiator input and output stream buffers from 5 bytes to 8 KiB. The larger buffers reduce socket system calls and protocol-framing overhead, improving throughput and CPU efficiency without changing the Extend wire protocol, configuration, or connection behavior. This change adds approximately 16 KiB of heap usage per physical Extend client connection.

Bugs fixed since Coherence CE v14.1.2-0-8

1. COH-33830 Fixed an issue in which POF serialization telemetry metric registration could deadlock with Coherence management failover while a cluster member was leaving. This could occur during rolling restarts and cause a WebLogic Server managed server to transition to the FAILED state. Metric metadata discovery no longer holds the metric registration lock, eliminating the lock-order inversion.
2. COH-33815 Fixed an issue where serialization-security telemetry could significantly degrade POF deserialization performance under concurrent load. Telemetry processing was optimized to reduce per-object overhead and contention while preserving serialization security checks.
3. COH-33788 Fixed an issue where SimpleMapIndex could overcount or undercount its memory footprint after repeated updates to collection-valued index entries. Footprint accounting now remains accurate as inverse mappings change or internal collections expand.
4. COH-33787 Fixed an issue that could cause high CPU utilization and repeated configuration-file I/O in deserialization-heavy workloads. When no explicit container-limit policy was configured, the default SerializationLimitPolicy could be resolved repeatedly from security and system-property configuration. This was particularly visible in the Extend POF decoding path, where the lookup could occur for every request.
5. COH-33773 Fixed an issue where Coherence Reporter repeatedly logged the same compatibility warnings during periodic report execution. Each warning category is now logged only once per JVM, reducing unnecessary log noise.
6. COH-33767 Fixed an issue where the JMX server could fail to start with an “Unsupported Reporter input” error when the Reporter configuration used an absolute file path without a file: prefix.
7. COH-33550 Fixed an issue where a cache configured with write-behind remove could report a negative size after entries were removed.

Full Changelog

Compare tags: 14.1.2-0-8...14.1.2-0-9