Fixes

This section provides information on the fixes for IBM webMethods Cloud Container v10.15.

Release 10.15.1

Issue ID Release Date Region Description
CLDP-5030 October 25, 2023
  • EU3 West Azure
 After upgrading the Jackson libraries, the JSON coder fails to decode strings that exceed a length of 1,000,000 characters. The issue is now resolved. Integration Server provides the watt.server.json.decode.maxStringLength parameter to override the limit on maximum string length. The default value is 20,000,000.

Configure the watt.server.json.decode.maxStringLength property specifically in the on-premises Integration Server setup and deploy the solution on Cloud Container. For more information, see Working with Extended Configuration Settings in IBM webMethods Microservices Runtime and IBM webMethods Integration Server Administrator's guide. Restart the Integration Server for changes to this parameter to take effect.
PIE-84157 September 16, 2023
  • US1 Oregon AWS
 Migrating from Integration Server 10.11 to 10.15 with custom code that uses AWS, results in joda-time library version conflict. This issue is now resolved.
BOC-19644 August 02, 2023
  • US1 Oregon AWS
  • EU2 Frankfurt AWS
  • EU3 West Azure
 After the Cloud Container 10.15 upgrade, during runtime if the pipeline for any webMethods Trading Networks services contain document headers by name "headers", the pipeline data becomes irretrievable, and end in service failures. Now, the document header with the name "headers" is allowed and the Trading Networks services run successfully.
PIE-83387 August 02, 2023
  • US1 Oregon AWS
  • EU2 Frankfurt AWS
  • EU3 West Azure
 To address this issue, Integration Server now includes the server configuration parameter watt.server.cache.iDataKey.toString that specifies whether a com.wm.data.IData object used as a key in one of the pub.cache services is converted to an immutable String before accessing the cache. Set to true to convert an IData object used as a key to a String. Set to false to keep the key as an IData object. The default is true. Integration Server does not need to be restarted for changes to this parameter to take effect.
Important: If the IData object is modified after it has been used as a key, Integration Server will not be able to retrieve values stored with the key regardless of the value of watt.server.cache.iDataKey.toString. IBM does not recommend using an IData object as a key with a cache as IData objects are mutable. Instead, use a java.lang.String object as a key.

Release 10.15.0

**Issue ID** **Release Date** **Region** **Description**
CLDP-4334 December 14, 2022 US2 East Azure EU3 West Azure Along with a minor improvement for tracking deployment status, a security enhancement is made to avoid vulnerabilities in third-party software from affecting IBM webMethods Cloud Container.