Object Store Connector Release Notes - Mule 4

Optimized the connector to improve its overall stability and performance.

Fixed a bug that caused the application to throw a generic MULE:UNKNOWN Mule error instead of the connector specific Mule errors OS:KEY_NOT_FOUND or OS:KEY_ALREADY_EXISTS. (COBJCON-6)

Fixed a bug that caused the application to fail when the ObjectStore v2 rate limit was reached inside a parallel for-each. (COBJCON-5)

Fixed a bug that caused two applications within the same domain couldn’t define top level object stores with the same name if the Object Store Connector dependency was declared in the domain. (MULE-18947)

Rely on underlying lock on store operation. (MULE-18232)

Fixed a race condition where ObjectStore store operation could throw ObjectAlreadyExistsException even when failIfPresent was set to false. (MULE-18232)

Avoid duplicated operations in order to improve performance. (MULE-16631)

Object Store operations should execute in the IO pool. (MULE-16409)

Message in exceptions references "null" as the ObjectStore name. (MULE-15285)

Top level ObjectStore throws NPE if used before application Start. (MULE-15210)

MUnit test fails with duplicated ObjectStore when running multiple suites. (MULE-15779)

Add name identifier to ObjectStoreManager injection to support CloudHub deployments. (MULE-14987)

ObjectStore connector does not work properly with MUnit tests when referencing a global. (MULE-14335)

Enables applications to store data for access by other applications

Stores key/value pair content

Works easily with Design Center