Boomi Runtime Updates & Release Notes

Fix

• Resolved an issue where runtime logged an unnecessary WARNING message for every connection and browse property map used by generic connectors. The warning had no effect on processing but added noise to container logs. When accepting this fix, the runtime version updates to version 26.11.3 and must be applied manually to resolve the issue for your account. Any runtime that has not taken the November release yet will be updated to 26.11.3 at the Platform release. Anyone who already took the November release will remain at 26.11.2. (RAS-1123)

New Features

• Introduced a unified Runtime section in the Platform dropdown that brings Flex Runtime and Integration Runtime documentation together in one place for easier navigation.

Enhancements

• Runtime Observability enhancements
  • Added support for HTTP transport protocol in addition to GRPC for Traces, Logs, and Metrics global endpoints. Current configurations default to GRPC to preserve existing behavior. (RUN-9946)
  • Added trace context propagation to outgoing requests for the REST and HTTP Client Connectors, so downstream consumers can correlate their telemetry. Propagation is enabled by default. (RUN-11583, RUN-11576)
  • Added the system.filesystem.local.inodes.usage and system.filesystem.local.inodes.limit metrics to telemetry. Telemetry now reports inode usage and limits for all supported container types. (RUN-11520)
• Enhanced confirmation dialogs for high-impact actions like deleting a runtime, deleting an environment, and attaching or detaching a runtime. This helps you avoid unintended clicks and accidental data loss. (RUN-11353)
• Improved processing of connector and process tracking messages, making execution data available on the platform faster. (RUN-11393)
• Java updates
  • Updated runtime cloud installers and upgraders to Java version 11.0.33.0.10, containing the latest security patches. (RUN-10360)

Fixes

• Resolved an API Gateway security issue. Refer to APIM-20736 for more information.
  • New Runtime version 26.11.2 will be the standard November runtime version for all customers. Customers using API Gateway are strongly encouraged to take this new version as soon as possible. (APIM-20747)
• Resolved an issue where enabling log or trace filtering without selecting a specific filter value silently exported all logs and traces. Filtering now correctly exports nothing when no filter value is selected. (RUN-11779)
• Resolved an issue where custom properties in the atom.vmoptions file did not save in the order you added them on the Custom Property tab. (RUN-597)
• Resolved an issue where environment extension updates restarted all listeners instead of only the affected ones. Extension changes now take effect more quickly. (RUN-2188)
• Resolved an issue where the worker maintenance task continued attempting to start workers for deleted cloud attachments, resulting in repeated InvalidAccountException errors in the runtime logs. (RUN-10436)
• Resolved an issue where new workers could start on a cloud cluster node while it was offboarding. Offboarding nodes now reject new workers immediately, ensuring a clean shutdown. (RUN-10405)
• Resolved an issue where sending multiple delete requests for the same runtime at the same time could cause database lock errors and failed deletions. Now, Boomi rejects duplicate delete requests for a runtime that's already being deleted. (RUN-11571)
• Resolved an issue where runtime service metrics didn’t export if the telemetry plugin started before those services were registered. The plugin now exports these metrics as soon as each service is available, without a restart. (RUN-11714)

Boomi Flex Runtime is now available in early access. Flex Runtime is a new self-hosted runtime you install in your own Kubernetes cluster, currently supporting Agentstudio agents invoked by the Agent step. This feature is available for the North America Boomi Platform. Sign up here to get started. To learn more, refer to Flex Runtime. (RAS-2)

Runtime Management UI is now available in early access. Runtime Management UI gives you an aggregated view of the runtimes in your account across Boomi services, starting with Flex Runtime. This feature is available for the North America Boomi Platform. To learn more, refer to Runtime Management UI. (RAS-160)

Released Integration runtime patch 26.09.3 that adds support for agent step execution on Flex Runtimes, enabling our Flex Runtime Early Access program. It introduces new agent step capabilities to run against agents deployed to Flex Runtimes. This patch is applicable only for customers participating in the Flex Runtime EA program and optional for all others.

Cluster Node ID and Execution Worker ID filtering:

• Added Cluster Node ID and Execution Worker ID filters to the Process Reporting page and the Extended Execution Information panel to help with troubleshooting.
• Added executionWorkerId and clusterNodeId query filters to the ExecutionRecord API, so you can troubleshoot issues with specific execution workers or cluster nodes. (RUN-6895)

Increased the default Maximum Execution Submissions value for Listen Workers from 10 to 100 to reflect a more realistic use case. (RUN-11553)

Observability Enhancements

• Added distributed tracing support for integration processes by capturing and exporting traceparent and tracestate header values per W3C standards, so you can correlate process executions with upstream API requests, including from Boomi's API Gateway. (RUN-10440)
• Added support for extracting the W3C traceparent header from incoming Shared Web Server requests, linking the caller's trace to the resulting integration process execution for end-to-end distributed tracing. (RUN-11350)
• Added JVM, operating system, and runtime infrastructure metrics — CPU, memory, filesystem, and file descriptor usage — to the OpenTelemetry plugin, so you can monitor infrastructure health without direct filesystem access. (RUN-11401, RUN-11421, RUN-10443)
• Added process.name to process log attributes and thread.id to trace attributes, so you can better identify and correlate processes and threads across logs and traces. (RUN-11216)
• Updated the service name reported to OpenTelemetry — across logs, metrics, and traces — to use the container name instead of the container UUID, so you can more easily identify the corresponding runtime. If this affects your OpenTelemetry dashboards, alerts, or scripts, update them to reference the container name or to use the existing runtime.id attribute. (RUN-11472)
• Improved trace visibility by adding dedicated span names for each submission handoff point as executions move from head node to execution worker. (RUN-11472)

Java and Docker updates

• Java updates:
  • Updated runtime cloud installers and upgraders to Java version 11.0.32.9.1, containing the latest security patches.
  • Applied the Java update to Boomi-hosted runtime clouds.
• Docker Image updates. Visit Dockerhub for more information
  • All V5 images are updated to Java version 11.0.32.9.1.
  • Red Hat image is updated to version 9.8-1786380870, containing the latest security patches.
• Other updates
  • Extended the security compatibility layer to preserve prior Certificate revocation list (CRL) size limit & and continued trust for certificates chaining to the Chunghwa Telecom root CA on the 2021.01 and 2024.11 compatibility levels after the recent Java upgrade. Integrations on the current default level receive the newer, stricter behavior. (RUN-11473)

(RUN-10359)

Fix

We fixed these issues

• Java updates:
  • Updated Boomi-hosted runtime test clouds to Java 11.0.31.11.1.
  • Updated Boomi-hosted runtime test clouds to Runtime version 26.07.2.
• Docker image updates. Visit Dockerhub for more information.
  • Updated all images to Java version 11.0.31.11.1
  • Updated the Alpine image to version 3.23.4, which includes the latest security patches.
  • Updated the Red Hat image to version 9.8-1781496742, which includes the latest security patches.

(RUN-11517, RUN-11527)

New

We added these features

• Java updates:
  • Runtime cloud installers and upgraders are updated to Java version 11.0.31.11.1, containing the latest security patches. (RUN-11418)

NOTE

If you have automatic Java updates scheduled, your runtime updates to Java version 11.0.31.11.1 on that existing schedule — within two weeks of this release — and restarts during the update.

Fix

We fixed these issues

• Resolved an issue where TLS handshake failures occurred when connecting to SQL Server using the Database, Database V2, or Azure connectors on Corretto JRE 11.0.31.11.1. If you experience this issue, set the Java Security Compatibility property to 2024.11. This fix is available in Non-MSV atom patch 26.07.2. (RUN-11418)

To learn more, refer to

Controlling Java security compatibility.