Skip to content

Coherence CE v14.1.1.0.2
Compare
Choose a tag to compare
@harveyraja harveyraja released this 21 Sep 23:42
14.1.1.0.2
84b21b1

This is patch 2 of the Coherence CE v14.1.1 release.

Fixed Issues

  • Improved recovering from persistence by deferring contentious maintenance tasks.
  • Fixed an issue where active recovery may commence while the service is suspended.
  • Fixed an issue where NonBlockingFiniteStateMachine.quiesceThenStop() does not shut down the state machine's event processing thread.
  • Fixed an issue where traffic over TLS 1.3 connections may hang.
  • Improved the description for the various managed-nodes options in a schema for coherence operational config so that it is easier for the developer to gain a quick understanding of what each mode means.
  • Fixed an issue in management over REST where an empty response could be returned instead of an expected empty collection.
  • Fixed an issue where partition distribution may fail to reach a balanced state within 5 minutes after recovering from a persistence snapshot.
  • Fixed an issue in CohQL where a StackOverflowError could be thrown when comparing two identifiers.
  • Fixed an issue in CohQL where backup and restore commands would use the default Java serializer rather than the pass-through binary serializer.
  • Fixed a race condition in ConfigurableCacheFactory where concurrent releaseCache() or destroyCache() calls could result in an IllegalArgumentException being thrown.
  • Fixed an issue in management over REST where the MBeanHelper incorrectly double-quotes scoped service names resulting in issues accessing service data.
  • Added additional improvement to the fix an issue where a service using active persistence may be terminated with a PersistenceException due to reaching the guardian timeout on a blocked operation.
  • Fixed an issue with the JVisualVM Plugin where it did not correctly function against Coherence-CE versions.
  • Fixed an issue where TcpRing may incorrectly trigger eviction of a temporarily network unreachable cluster member.
  • Fixed an issue where partition distribution for a large cluster could take a long time to reach the desired state.
  • Added security enhancement that enables configuring between secure static lambdas and more convenient to use dynamic lambdas.
  • Fixed an issue where a registered MapTrigger may not be called.
  • Fixed a non-optimal deadlock avoidance rollback when using BackingMapContext.getBackingMapEntry to enlist entries in a different cache while concurrently executing a invokeAll on the other cache.
Assets 2
Loading