From b951837f0c8a4f0dffa0df6d2c679c2c6b5f9453 Mon Sep 17 00:00:00 2001 From: Daniela Merlo Date: Mon, 21 Jul 2025 15:15:48 -0300 Subject: [PATCH 01/33] W-19098665-deprecateTLS1.x-49-dm --- modules/ROOT/pages/securing.adoc | 2 +- modules/ROOT/pages/tls-configuration.adoc | 13 ++++++------- 2 files changed, 7 insertions(+), 8 deletions(-) diff --git a/modules/ROOT/pages/securing.adoc b/modules/ROOT/pages/securing.adoc index bf67d1365..fd81177d2 100644 --- a/modules/ROOT/pages/securing.adoc +++ b/modules/ROOT/pages/securing.adoc @@ -60,7 +60,7 @@ Perform component authorization, or use it as a Mule security provider. Configure authorization using Spring Security features on your Mule components, so that users with different roles can only invoke certain methods. == TLS Configuration -TLS is a cryptographic protocol that provides communications security for your Mule app. Mule 4.x supports Transport Layer Security (TLS) 1.1 and 1.2. +TLS is a cryptographic protocol that provides communications security for your Mule app. Mule 4.x supports Transport Layer Security (TLS) 1.2 and 1.3. See details in xref:tls-configuration.adoc[TLS Configuration] diff --git a/modules/ROOT/pages/tls-configuration.adoc b/modules/ROOT/pages/tls-configuration.adoc index a53262448..9e4f3fa75 100644 --- a/modules/ROOT/pages/tls-configuration.adoc +++ b/modules/ROOT/pages/tls-configuration.adoc @@ -17,7 +17,6 @@ TLS compatibility differs by Mule deployment model and TLS version. |TLS Version |On-Premises|CloudHub|Anypoint Runtime Fabric |1.3|Supported when running Mule on a JDK that supports TLS 1.3 but _not_ enabled by default|Supported for Mule apps hosted in this deployment model|Supported and enabled when running on a JDK that supports TLS 1.3 |1.2 3+|Supported and enabled by all deployment models -|1.1 3+|Supported and enabled by all deployment models |=== == The tls:context Element @@ -110,7 +109,7 @@ To fully configure TLS for a Mule app: == Keystore Generation -The standard JDK distribution does not include a keystore by default, use `keytool` to generate your keystores and certificates. The keystore you generate contains a private key and a public certificate. This certificate is self-signed so it is not to be trusted by clients unless you share the public certificate with them. +The standard JDK distribution doesn't include a keystore by default, use `keytool` to generate your keystores and certificates. The keystore you generate contains a private key and a public certificate. This certificate is self-signed so it isn't to be trusted by clients unless you share the public certificate with them. === Requirements @@ -138,7 +137,7 @@ Replace `` with the name you want for your keystore. Optionally, you can set the encryption algorithm to ECDSA by specifying `-keyalg EC` instead of `-keyalg RSA`. + [IMPORTANT] -If you do not specify the encryption algorithm, the tool uses DSA by default which is not compatible with TLS 1.2 and causes the SSL handshake to fail when the Mule app receives an HTTPS request. +If you don't specify the encryption algorithm, the tool uses DSA by default which isn't compatible with TLS 1.2 and causes the SSL handshake to fail when the Mule app receives an HTTPS request. . Respond to the tool's prompts. The following output shows example responses: @@ -210,7 +209,7 @@ After you receive the CA's signature, you can import the signed certificate file keytool -import -keystore .jks -alias -file ---- -Replace `` with the a new desired value, the alias you define must not be linked to any existing key or the process fails. + +Replace `` with the a new desired value, the alias you define mustn't be linked to any existing key or the process fails. + Replace `` with the same value used in the previous steps. + Replace `` with the name of the signed certificate you received from the Certification Authority. @@ -334,7 +333,7 @@ To configure protocols and cipher suites in the Mule runtime: . The Mule admin edits the `/conf` directory in `$MULE_HOME`. `$MULE_HOME` points to the directory where your Mule installation resides, for example `/opt/mule-4.0`. Select the appropriate file where you specify the cipher suites and protocols: + -** `tls-default.conf` allows fine-tuning when Mule is not configured to run in Federal Information Processing Standards (FIPS) security mode. +** `tls-default.conf` allows fine-tuning when Mule isn't configured to run in Federal Information Processing Standards (FIPS) security mode. + ** `tls-fips140-2.conf` allows fine-tuning when Mule is running in FIPS security mode. + @@ -345,7 +344,7 @@ Open the relevant file and comment or uncomment items in the lists to manually c In the `tls:context` element, you can only reference protocols or cipher suites that are included in the Mule global TLS configuration file or defaults. In `tls:context`, set `enabledProtocols` and `enabledCipherSuite` for a Mule app to the value `default`. After these values are set, TLS uses the following protocols and cipher suites: * Those configured in your global TLS configuration if it exists -* The defaults provided by your Java environment if a global TLS configuration does not exist +* The defaults provided by your Java environment if a global TLS configuration doesn't exist Cipher suite names can be long and reduce the readability of your XML code. To improve readability, keep these names in an external properties file in your Mule project. You can then reference the properties. For example: @@ -417,7 +416,7 @@ This example sets up two-way authentication (also called mutual authentication), This example uses the `insecure` property to disable validations for prototyping and development. [IMPORTANT] -Do not use the `insecure` property in production environments. +Don't use the `insecure` property in production environments. [source,xml,linenums] ---- From b83e079d785856c6a6bd317ed95949d6c3255a8e Mon Sep 17 00:00:00 2001 From: Daniela Merlo Date: Tue, 26 Aug 2025 17:54:24 -0300 Subject: [PATCH 02/33] W-19420663-MuleTroubleshootingPlugin-49-dm --- modules/ROOT/nav.adoc | 1 + .../ROOT/pages/mule-troubleshooting-tool.adoc | 399 ++++++++++++++++++ 2 files changed, 400 insertions(+) create mode 100644 modules/ROOT/pages/mule-troubleshooting-tool.adoc diff --git a/modules/ROOT/nav.adoc b/modules/ROOT/nav.adoc index 9d4aa9b98..30521e9ce 100644 --- a/modules/ROOT/nav.adoc +++ b/modules/ROOT/nav.adoc @@ -49,6 +49,7 @@ include::partial$nav-app-dev.adoc[] *** xref:creating-and-managing-a-cluster-manually.adoc[Create and Manage a Cluster Manually] *** xref:hadr-guide.adoc[High Availability and Disaster Recovery] * xref:mule-upgrade-tool.adoc[Mule Upgrade Tool] +* xref:mule-troubleshooting-tool.adoc[Mule Troubleshooting Tool] * xref:using-maven-with-mule.adoc[Maven Support in Mule] ** xref:mmp-concept.adoc[Mule Maven Plugin] ** xref:package-a-mule-application.adoc[Package a Mule Application] diff --git a/modules/ROOT/pages/mule-troubleshooting-tool.adoc b/modules/ROOT/pages/mule-troubleshooting-tool.adoc new file mode 100644 index 000000000..b593a3c4b --- /dev/null +++ b/modules/ROOT/pages/mule-troubleshooting-tool.adoc @@ -0,0 +1,399 @@ += Mule Troubleshooting Tool +ifndef::env-site,env-github[] +include:: +endif::[] + +Use the Mule Troubleshooting tool to generate structured diagnostic information, simplify troubleshooting, and provide consistent data for Mule runtime support. + +The Mule Troubleshooting tool provides a unified way to collect diagnostic data from Mule runtime environments. It generates a structured diagnostic archive called the Diagnostic Information Analysis File (DIAF), which consolidates Mule runtime information, application metrics, and system data into a single, standardized output. + +This Java-based tool provides an extensible, environment-agnostic solution that simplifies troubleshooting for Mule runtime engineers, MuleSoft Support teams, customers running self-service diagnostics, and AI-assisted analysis. + +== Before You Begin + +Before starting your upgrade, make sure that you have the following prerequisites: + +* Mule runtime distribution starting with 4.10, with patches available for 4.6 and 4.9. +* Java 8 or later, matching the Mule runtime version requirements. +* Access to `$MULE_HOME`. The CLI script `diag` automatically locates the Mule home directory. + +The tool works out-of-the-box in all deployment models (Standalone, CloudHub, CloudHub 2.0, Runtime Fabric) without installing additional dependencies. + +== Using the Mule Troubleshooting Tool + +Run the following command from your Mule runtime installation at `$MULE_HOME/tools/diag` to generate the DIAF and a thread dump. By default, this creates a ZIP file named `mule_dump_[timestamp].diaf`. +Use the `./diag --support` command to generate a heap dump. The Mule dump is saved in the `logs` directory by default, or use the `./diag --output` command to save the dump to a different path. + +The tool's help output lists the available commands and options. + +[source,bash] +---- +➜ mule-enterprise-standalone-4.6.21-SNAPSHOT ./tools/diag help +Mule Troubleshooting Tool +========================= + +Usage: ./diag [options] [command] [command-options] + +Commands: + diaf Generate a complete Mule diagnostic dump (default) + help Show this help message + Execute a specific troubleshooting operation + +Global Options: + --stdout Output the diagnostic dump to standard output + --output Specify custom output directory or file path + --support Enable support mode (includes heap dump) + --debug Enable debug mode with remote debugging on port 5005 + +Examples: + ./diag # Generate diagnostic dump to logs directory + ./diag --stdout # Output diagnostic dump to stdout + ./diag --support # Include heap dump in diagnostic + ./diag --output /tmp/mule.zip # Save to specific file + ./diag --output /tmp/ # Save to specific directory + ./diag # Execute specific operation + +Output: + By default, the tool creates a ZIP file containing: + - mule_dump_.diaf # Diagnostic information + - thread_dump_.txt # Thread dump + - heap_dump_.hprof # Heap dump (if --support is used) + + The ZIP file is saved to the 'logs' directory by default. +---- + +== Diagnostic Information Analysis File (DIAF) Contents + +The Diagnostic Information Analysis File (DIAF) groups all diagnostic data collected by the Mule Troubleshooting tool into structured sections. Use this reference to understand the content of each section: + +* <> +* <> +* <> +* <> +* <> +* <> + +[[diaf-title]] +=== Title + +This section shows the report generation timestamp. + +[cols="1,3", options="header"] +|=== +| Field | Description + +| Report Generation Timestamp +| The report generation time, expressed in the local time zone. +|=== + +[[diaf-basic-info]] +=== Basic Information + +This section shows details about the environment where the Mule runtime instance is running. + +[cols="1,3", options="header"] +|=== +| Field | Description + +| Mule Product/version +| The product (CE/EE), version, and build number of the Mule runtime. Formatted as `[productName] [version] (build [buildNumber])`. + +| `mule_home` +| Absolute path to `MULE_HOME` for the Mule runtime. + +| `mule_base` +| Absolute path to MULE_BASE for the Mule runtime. + +| `mule.*` System Properties +| All system properties starting with `mule.`, including those defined by DataWeave and API Gateway. Listed with values and sorted alphabetically. + +| Java Version +| Version of the JVM running the Mule runtime. + +| Java Vendor +| Vendor of the JVM running the Mule runtime. + +| Java VM Name +| Full name of the JVM running the Mule runtime. + +| `JAVA_HOME` +| Location of the JVM running the Mule runtime. + +| OS Name +| Name of the OS running the Mule runtime. + +| OS Version +| Version of the OS running the Mule runtime. + +| OS Arch +| Architecture of the OS (for example, `amd64`, `aarch`). + +| Running Time +| The total time the Mule runtime has been running. + +| PID +| Process ID of the JVM running the Mule runtime. + +| Report Millis Time +| Report generation time in milliseconds since epoch (`System.currentTimeMillis`). + +| Report Nano Time +| Report generation time in nanoseconds (`System.nanoTime`). + +| `memory.used` +| Amount of used memory in the JVM. + +| `memory.free` +| Amount of free memory in the JVM. + +| `memory.total` +| Total amount of memory in the JVM. + +| `memory.max` +| Maximum amount of memory the JVM attempt to use. + +| `memory.used/total` +| Percentage of used memory compared to the total allocated memory. + +| `memory.used/max` +| Percentage of used memory compared to the maximum available memory. + +| `load.process` +| Percentage of recent CPU usage for the JVM process; negative value if unavailable. + +| `load.system` +| Percentage of recent CPU usage for the whole system; negative value if unavailable. + +| `load.systemAverage` +| System load average for the last minute; negative value if unavailable. +|=== + +[[diaf-statistics]] +=== Statistics + +This section shows detailed statistics information about deployed Mule applications and their performance metrics. + +==== General Application Metrics + +[cols="1,3", options="header"] +|=== +| Field | Description + +| Events Received +| Number of events received by the application or flow. + +| Events Processed +| Number of events processed by the application or flow. + +| Messages Dispatched +| Total number of messages dispatched from message sources within the application. + +| Execution Errors +| Number of execution errors encountered. + +| Fatal Errors +| Number of fatal errors that cause the application to fail or stop processing. + +| Connection Errors +| Number of connection-related errors that occur. + +| Average Processing Time +| Average time (in milliseconds) required to process an event. + +| Min Processing Time +| Minimum time (in milliseconds) required to process an event. + +| Max Processing Time +| Maximum time (in milliseconds) required to process an event. + +| Total Processing Time +| Cumulative time (in milliseconds) spent processing all events. +|=== + +==== Flow Summary Statistics + +[cols="1,3", options="header"] +|=== +| Field | Description + +| Private Flows Declared +| Total number of private flows declared in the application. A private flow doesn't contain a `MessageSource` and isn't used by an APIkit router. + +| Private Flows Active +| Number of private flows that are currently in a started state. + +| Trigger Flows Declared +| Total number of trigger flows declared in the application. A trigger flow contains a MessageSource. + +| Trigger Flows Active +| Number of trigger flows currently in a started state. + +| API Kit Flows Declared +| Total number of APIkit flows declared in the application. An APIkit flow is used by an APIkit router but doesn't contain a `MessageSource`. + +| API Kit Flows Active +| Number of APIkit flows currently in a started state. +|=== + +==== Flow Statistics + +[cols="1,3", options="header"] +|=== +| Field | Description + +| Events Received +| Total number of events received by the application since it started. + +| Events Processed +| Total number of events successfully processed by the application. + +| Messages Dispatched +| Total number of messages dispatched from message sources within the application. + +| Execution Errors +| Number of execution errors that occur during event processing. + +| Fatal Errors +| Number of fatal errors that cause the application to fail or stop processing. + +| Connection Errors +| Number of connection-related errors that occur. + +| Average Processing Time +| Average time (in milliseconds) required to process an event. +|=== + +[[diaf-fuse-board]] +=== Fuse Board + +This section shows alerts for known Mule runtime issues. The report lists how many times each alert triggers during the last 1, 5, 15, and 60 minutes along with the context of the alert at the time of triggering. Some alerts trigger multiple times with the same context, such as the backpressure alert, so the tool shows the context once and indicates how many times it happens to avoid flooding the report. Alerts that don't trigger in any of the time intervals aren't included in the report. + +[cols="1,3", options="header"] +|=== +| Field | Description + +| `MULE:UNKNOWN` error raised +| `MULE:UNKNOWN` errors are generated by the runtime and go unhandled. If such an error raises or appears in the app log, it indicates a bug in the Mule runtime. The context shows the details of the errors catalogued as `MULE:UNKNOWN`. + +| Reactor discarded event +| A discarded event is one that a component explicitly filters in a flow. This effectively cuts the processing of such event, causing the execution to hang. The context shows the correlation ID of each discarded event. + +| Reactor dropped event +| A dropped event doesn't properly pass to the following component in a flow through a reactor chain and doesn't complete. Its symptom is that the event is “hanged”. No context is shown for this alert because information is already available in the event dump. + +| Reactor dropped error +| A dropped error doesn't properly pass to the corresponding error handler in a flow through a reactor chain, and so doesn't complete. Its symptom is that the event is “hanged” when an error occurs. The context shows the string representation of each dropped error. + +| Not consumed stream +| A stream that is garbage collected before being completely consumed may provoke leaks on certain conditions (the most common one is connections from a DB connection pool that remain taken until the data is fully read). The context shows the originating location of the components that generated the streams. + +| Backpressure triggered +| Backpressure is the mechanism by which incoming events in excess of current capacity are rejected. This happens because of a spike of incoming events or a longer than usual processing time of the flows. A common sign is when backpressure triggers on systems that have a CPU and memory capacity. The context shows the flow or component that exceeded capacity and the reason for backpressure. + +| XA recovery start error +| Triggered when recovery of an XA connection fails to start. The context shows the unique name (including the config name) of the connection for which recovery fails. + +| Async logger ringbuffer full +| When a log appender writes logs slower than the log entries are generated, the logger ringbuffer fills up. When full, threads attempting to log either wait for space in the ringbuffer or log synchronously, depending on the configuration. In either case, a thread that shouldn't block or wait does so, causing performance issues in the Mule runtime. No context is available for this alert because it always means the same, the buffer is full. +|=== + +[NOTE] +-- +Keep in mind that this report provides hints about what might be causing an issue. For details on a specific alert, query the log. This report isn't intended to replace the log for detailed analysis. +-- + +[[diaf-event-dump]] +=== Event Dump + +This section shows a hierarchical listing of in-flight events. For each event hierarchy executing through a flow in Mule has at least one entry in the report. For each child context for the event, a nested entry appears, sorted in a stack order: children on top, parents on bottom. If an event is dropped, the legend `DROPPED` appears next to it. + +[cols="1,3", options="header"] +|=== +| Field | Description + +| `eventId` +| A unique identifier for the event. For child events, it has the ID of the parent event context as prefix. + +| `runningTime` +| How long the event has been running. For child events, this time refers to the execution of this child context. The format is “mm:ss”. + +| `eventContextState` +a| +* `EXECUTING`: Event is being executing by the flow or executable component, or has finished but the response is still being processed. +* `RESPONSE_PROCESSED`: Event execution is complete and the response is handled. +* `COMPLETE`: Same as `RESPONSE_PROCESSED`, and all child events are `RESPONSE_PROCESSED`. +* `TERMINATED`: After `COMPLETE`, and all completion callbacks of the context execute. + +| `flowStack` +a| `flowStack` is composed by zero-to-many lines, each with this format. +[source,xml] +---- +at [componentId]@[componentLocation]([muleFileName]:[muleFileLineNumber]) [timeInLocation] ms +---- + +| `flowStack.componentId` +| Identifier of the component (for example, `http:request`). + +| `flowStack.componentLocation` +| Unique identifier of a component within a Mule application. The first part is the flow or policy name, followed by the index and chains where the component is nested. + +| `flowStack.muleFileName` +| Name of the Mule config file where the component is located. + +| `flowStack.muleFileLineNumber` +| Line number in the Mule configuration file where the component is located. + +| `flowStack.timeInLocation` +| Duration in milliseconds the event spends at the `flowStack` entry. +|=== + +[[diaf-schedulers]] +=== Schedulers + +This section shows the status and metrics of each scheduler. For Mule runtime instances with multiple deplyed applications, entries are grouped by application. + +[cols="1,3", options="header"] +|=== +| Field | Description + +| `schedulerName` +| Name assigned to the scheduler when created, showing where in the code it happened. + +| `threadType` +a| Type of tasks the scheduler runs: + +* `IO`: A task that spends most of its execution waiting for I/O operations to complete. +* `CPU_INTENSIVE`: A task that runs longer than 10 milliseconds, with less than 20% of time blocked. +* `CPU_LIGHT`: A task that never blocks and runs is less than 10 milliseconds. +* `CUSTOM`: Threads that aren't managed by Mule runtime or shared between schedulers. Used when a thread pool needs exclusive use (for example, NIO selectors). + +| `shutdown` +| A shutdown scheduler doesn't accept new tasks. Tasks still running are allowed a graceful period to complete. + +| `terminated` +| A terminated scheduler is shut down and all in progress tasks are completed or forcefully terminated after a graceful shutdown period. + +| `activeTasks` +| Number of tasks currently executing by the scheduler. + +| `queuedTasks` +| Number of tasks waiting in a queue. Not shown if there's no queue, the queue size can't be queried, or no tasks are queued. + +| `rejections` +| Number of tasks rejected because the scheduler is at capacity. Shows rejections in the last 1, 5, 15, and 601 minutes. If there aren't any in those intervals, the alert isn't shown. + +| `throttles` +| Number of tasks throttled because the scheduler is at capacity. Shows throttles in the last 1, 5, 15, and 601 minutes. If there aren't any in those intervals, the alert isn't shown. +|=== + +== Technical Considerations + +* DIAF provides investigation hints. Check the logs for complete details. +* Heap dumps may contain sensitive data. Enable `--support` only in secure environments. +* In Mule runtime instances with multiple applications, DIAF sections are grouped by application. + +== Best Practices + +* Use DIAF for initial troubleshooting before collecting heap or thread dumps manually. +* Correlate events in the event dump section with logs by using the `eventId` for deeper analysis. +* Collect schedule diagnostics during maintenance windows in production environments. \ No newline at end of file From 5f8a024c9d31d931c0c249ce750d5e82215a48c4 Mon Sep 17 00:00:00 2001 From: Daniela Merlo <97902112+dmerlob@users.noreply.github.com> Date: Tue, 26 Aug 2025 18:00:37 -0300 Subject: [PATCH 03/33] w-19420663-update note --- modules/ROOT/pages/mule-troubleshooting-tool.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/modules/ROOT/pages/mule-troubleshooting-tool.adoc b/modules/ROOT/pages/mule-troubleshooting-tool.adoc index b593a3c4b..e72c5db11 100644 --- a/modules/ROOT/pages/mule-troubleshooting-tool.adoc +++ b/modules/ROOT/pages/mule-troubleshooting-tool.adoc @@ -299,7 +299,7 @@ This section shows alerts for known Mule runtime issues. The report lists how ma [NOTE] -- -Keep in mind that this report provides hints about what might be causing an issue. For details on a specific alert, query the log. This report isn't intended to replace the log for detailed analysis. +The report provides hints about potential issues. For details on a specific alert, query the log. This report isn't intended to replace the log for detailed analysis. -- [[diaf-event-dump]] @@ -396,4 +396,4 @@ a| Type of tasks the scheduler runs: * Use DIAF for initial troubleshooting before collecting heap or thread dumps manually. * Correlate events in the event dump section with logs by using the `eventId` for deeper analysis. -* Collect schedule diagnostics during maintenance windows in production environments. \ No newline at end of file +* Collect schedule diagnostics during maintenance windows in production environments. From a231fb17f799c51f746fd982bb758de2f4ba69e7 Mon Sep 17 00:00:00 2001 From: Daniela Merlo <97902112+dmerlob@users.noreply.github.com> Date: Wed, 27 Aug 2025 10:05:27 -0300 Subject: [PATCH 04/33] Update modules/ROOT/pages/mule-troubleshooting-tool.adoc --- modules/ROOT/pages/mule-troubleshooting-tool.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/ROOT/pages/mule-troubleshooting-tool.adoc b/modules/ROOT/pages/mule-troubleshooting-tool.adoc index e72c5db11..033a119b7 100644 --- a/modules/ROOT/pages/mule-troubleshooting-tool.adoc +++ b/modules/ROOT/pages/mule-troubleshooting-tool.adoc @@ -21,7 +21,7 @@ The tool works out-of-the-box in all deployment models (Standalone, CloudHub, Cl == Using the Mule Troubleshooting Tool -Run the following command from your Mule runtime installation at `$MULE_HOME/tools/diag` to generate the DIAF and a thread dump. By default, this creates a ZIP file named `mule_dump_[timestamp].diaf`. +Run the following command from your Mule runtime installation at `$MULE_HOME/tools/diag` to generate the DIAF and a thread dump. By default, this creates a ZIP file named `mule_dump_[timestamp].zip`. Use the `./diag --support` command to generate a heap dump. The Mule dump is saved in the `logs` directory by default, or use the `./diag --output` command to save the dump to a different path. The tool's help output lists the available commands and options. From 84d9b4835992c4921ca83f12efa1b765b19d05c3 Mon Sep 17 00:00:00 2001 From: Daniela Merlo Date: Wed, 10 Sep 2025 16:12:57 -0300 Subject: [PATCH 05/33] W-19449965-Mule-410-dm --- antora.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/antora.yml b/antora.yml index a2d817f27..718becdeb 100644 --- a/antora.yml +++ b/antora.yml @@ -1,6 +1,6 @@ name: mule-runtime title: Mule Runtime version: '4.9' -display_version: '4.9' +display_version: '4.10' nav: - modules/ROOT/nav.adoc From 4c0f31dd3383aeb10ad9d1c6319047d90150cbe5 Mon Sep 17 00:00:00 2001 From: Daniela Merlo Date: Wed, 10 Sep 2025 16:45:08 -0300 Subject: [PATCH 06/33] Typos (fixing build errors) --- modules/ROOT/pages/_partials/mmp-deploy-to-rtf.adoc | 4 ++-- modules/ROOT/pages/migration-mel.adoc | 8 +++----- 2 files changed, 5 insertions(+), 7 deletions(-) diff --git a/modules/ROOT/pages/_partials/mmp-deploy-to-rtf.adoc b/modules/ROOT/pages/_partials/mmp-deploy-to-rtf.adoc index ee54378a5..f5f6f190c 100644 --- a/modules/ROOT/pages/_partials/mmp-deploy-to-rtf.adoc +++ b/modules/ROOT/pages/_partials/mmp-deploy-to-rtf.adoc @@ -17,7 +17,7 @@ If you want to deploy applications to Runtime Fabric using a different method, s * Ensure that the Mule Maven Plugin is added to your project + -See xref:mmp-concept.adoc#add-mmp[Add the Mule Maven Plugin to a Mule Project] for instructions. +See xref:mule-runtime::mmp-concept.adoc#add-mmp[Add the Mule Maven Plugin to a Mule Project] for instructions. * You understand and have available the number of resources required to deploy to Runtime Fabric + See xref:runtime-fabric::deploy-resource-allocation-self-managed.adoc[]for more information. * The application is already published in Exchange + @@ -30,7 +30,7 @@ See xref:exchange::to-publish-assets-maven.adoc[Publish and Deploy Exchange Asse * Ensure that the Mule Maven Plugin is added to your project + -See <> for instructions. +See xref:mule-runtime::mmp-concept.adoc#add-mmp[Add the Mule Maven Plugin to a Mule Project] for instructions. * You understand and have available the number of resources required to deploy to Runtime Fabric + See xref:runtime-fabric::deploy-resource-allocation-self-managed.adoc[Resource Allocation on Anypoint Runtime Fabric] for more information. * The application is already published in Exchange + diff --git a/modules/ROOT/pages/migration-mel.adoc b/modules/ROOT/pages/migration-mel.adoc index de6243f15..1c84377c9 100644 --- a/modules/ROOT/pages/migration-mel.adoc +++ b/modules/ROOT/pages/migration-mel.adoc @@ -417,10 +417,10 @@ can be used instead. The next example shows how a regex is used in DataWeave to == See Also -xref:dataweave.adoc[DataWeave Language] - -https://blogs.mulesoft.com/dev/mule-dev/why-dataweave-main-expression-language-mule-4/[Why DataWeave is the Main Expression Language in Mule 4 Beta] +* xref:dataweave.adoc[DataWeave Language] +* https://blogs.mulesoft.com/dev/mule-dev/why-dataweave-main-expression-language-mule-4/[Why DataWeave is the Main Expression Language in Mule 4 Beta] +//// * MEL expressions to DataWeave 2.x (2.1?) * Preliminary plan is to take examples from Mule 3 docs and show how to migrate them to 4.0. See https://docs.mulesoft.com/mule-user-guide/v/3.9/mule-expression-language-mel * 3 primary use cases (from Dan Feist): @@ -482,9 +482,7 @@ FROM ANA'S BLOG: == Date Time * MEL: `#[payload.name ++ '.' ++ dataType.mimeType.subType]` * DataWeave: `#[payload ++ { date : now() }]` -//// -//// Note: Mariano G. says most people using MEL to access the payload. For simple expressions, migration tool will do it, but we will have to help migrate complex mappings. No date on migrator, but is first priority after GA. Somewhere in the Mule. From 79a5af7df57996722b95e4f98413da57ca24a9a6 Mon Sep 17 00:00:00 2001 From: Daniela Merlo Date: Wed, 10 Sep 2025 17:55:24 -0300 Subject: [PATCH 07/33] w-19420663-updating doc --- modules/ROOT/nav.adoc | 2 +- ....adoc => mule-troubleshooting-plugin.adoc} | 30 +++++++++---------- 2 files changed, 16 insertions(+), 16 deletions(-) rename modules/ROOT/pages/{mule-troubleshooting-tool.adoc => mule-troubleshooting-plugin.adoc} (87%) diff --git a/modules/ROOT/nav.adoc b/modules/ROOT/nav.adoc index 30521e9ce..cd4d4e586 100644 --- a/modules/ROOT/nav.adoc +++ b/modules/ROOT/nav.adoc @@ -49,7 +49,7 @@ include::partial$nav-app-dev.adoc[] *** xref:creating-and-managing-a-cluster-manually.adoc[Create and Manage a Cluster Manually] *** xref:hadr-guide.adoc[High Availability and Disaster Recovery] * xref:mule-upgrade-tool.adoc[Mule Upgrade Tool] -* xref:mule-troubleshooting-tool.adoc[Mule Troubleshooting Tool] +* xref:mule-troubleshooting-plugin.adoc[Mule Troubleshooting Plugin] * xref:using-maven-with-mule.adoc[Maven Support in Mule] ** xref:mmp-concept.adoc[Mule Maven Plugin] ** xref:package-a-mule-application.adoc[Package a Mule Application] diff --git a/modules/ROOT/pages/mule-troubleshooting-tool.adoc b/modules/ROOT/pages/mule-troubleshooting-plugin.adoc similarity index 87% rename from modules/ROOT/pages/mule-troubleshooting-tool.adoc rename to modules/ROOT/pages/mule-troubleshooting-plugin.adoc index 033a119b7..0f88e86c6 100644 --- a/modules/ROOT/pages/mule-troubleshooting-tool.adoc +++ b/modules/ROOT/pages/mule-troubleshooting-plugin.adoc @@ -1,30 +1,30 @@ -= Mule Troubleshooting Tool += Mule Troubleshooting Plugin ifndef::env-site,env-github[] include:: endif::[] -Use the Mule Troubleshooting tool to generate structured diagnostic information, simplify troubleshooting, and provide consistent data for Mule runtime support. +Use the Mule Troubleshooting plugin to generate structured diagnostic information, simplify troubleshooting, and provide consistent data for Mule runtime support. -The Mule Troubleshooting tool provides a unified way to collect diagnostic data from Mule runtime environments. It generates a structured diagnostic archive called the Diagnostic Information Analysis File (DIAF), which consolidates Mule runtime information, application metrics, and system data into a single, standardized output. +The Mule Troubleshooting plugin provides a unified way to collect diagnostic data from Mule runtime environments. It generates a structured diagnostic archive called the Diagnostic Information Analysis File (DIAF), which consolidates Mule runtime information, application metrics, and system data into a single, standardized output. -This Java-based tool provides an extensible, environment-agnostic solution that simplifies troubleshooting for Mule runtime engineers, MuleSoft Support teams, customers running self-service diagnostics, and AI-assisted analysis. +This Java-based plugin provides an extensible, environment-agnostic solution that simplifies troubleshooting for Mule runtime engineers, MuleSoft Support teams, customers running self-service diagnostics, and AI-assisted analysis. == Before You Begin -Before starting your upgrade, make sure that you have the following prerequisites: +Before using the plugin, make sure that you have the following prerequisites: * Mule runtime distribution starting with 4.10, with patches available for 4.6 and 4.9. * Java 8 or later, matching the Mule runtime version requirements. * Access to `$MULE_HOME`. The CLI script `diag` automatically locates the Mule home directory. -The tool works out-of-the-box in all deployment models (Standalone, CloudHub, CloudHub 2.0, Runtime Fabric) without installing additional dependencies. +The plugin works out-of-the-box in all deployment models (Standalone, CloudHub, CloudHub 2.0, Runtime Fabric) without installing additional dependencies. -== Using the Mule Troubleshooting Tool +== Using the Mule Troubleshooting Plugin Run the following command from your Mule runtime installation at `$MULE_HOME/tools/diag` to generate the DIAF and a thread dump. By default, this creates a ZIP file named `mule_dump_[timestamp].zip`. Use the `./diag --support` command to generate a heap dump. The Mule dump is saved in the `logs` directory by default, or use the `./diag --output` command to save the dump to a different path. -The tool's help output lists the available commands and options. +The plugin's help output lists the available commands and options. [source,bash] ---- @@ -64,7 +64,7 @@ Output: == Diagnostic Information Analysis File (DIAF) Contents -The Diagnostic Information Analysis File (DIAF) groups all diagnostic data collected by the Mule Troubleshooting tool into structured sections. Use this reference to understand the content of each section: +The Diagnostic Information Analysis File (DIAF) groups all diagnostic data collected by the Mule Troubleshooting plugin into structured sections. Use this reference to understand the content of each section: * <> * <> @@ -150,7 +150,7 @@ This section shows details about the environment where the Mule runtime instance | Total amount of memory in the JVM. | `memory.max` -| Maximum amount of memory the JVM attempt to use. +| Maximum amount of memory the JVM attempts to use. | `memory.used/total` | Percentage of used memory compared to the total allocated memory. @@ -266,7 +266,7 @@ This section shows detailed statistics information about deployed Mule applicati [[diaf-fuse-board]] === Fuse Board -This section shows alerts for known Mule runtime issues. The report lists how many times each alert triggers during the last 1, 5, 15, and 60 minutes along with the context of the alert at the time of triggering. Some alerts trigger multiple times with the same context, such as the backpressure alert, so the tool shows the context once and indicates how many times it happens to avoid flooding the report. Alerts that don't trigger in any of the time intervals aren't included in the report. +This section shows alerts for known Mule runtime issues. The report lists how many times each alert triggers during the last 1, 5, 15, and 60 minutes along with the context of the alert at the time of triggering. Some alerts trigger multiple times with the same context, such as the backpressure alert, so the plugin shows the context once and indicates how many times it happens to avoid flooding the report. Alerts that don't trigger in any of the time intervals aren't included in the report. [cols="1,3", options="header"] |=== @@ -350,7 +350,7 @@ at [componentId]@[componentLocation]([muleFileName]:[muleFileLineNumber]) [timeI [[diaf-schedulers]] === Schedulers -This section shows the status and metrics of each scheduler. For Mule runtime instances with multiple deplyed applications, entries are grouped by application. +This section shows the status and metrics of each scheduler. For Mule runtime instances with multiple deployed applications, entries are grouped by application. [cols="1,3", options="header"] |=== @@ -380,10 +380,10 @@ a| Type of tasks the scheduler runs: | Number of tasks waiting in a queue. Not shown if there's no queue, the queue size can't be queried, or no tasks are queued. | `rejections` -| Number of tasks rejected because the scheduler is at capacity. Shows rejections in the last 1, 5, 15, and 601 minutes. If there aren't any in those intervals, the alert isn't shown. +| Number of tasks rejected because the scheduler is at capacity. Shows rejections in the last 1, 5, 15, and 60 minutes. If there aren't any in those intervals, the alert isn't shown. | `throttles` -| Number of tasks throttled because the scheduler is at capacity. Shows throttles in the last 1, 5, 15, and 601 minutes. If there aren't any in those intervals, the alert isn't shown. +| Number of tasks throttled because the scheduler is at capacity. Shows throttles in the last 1, 5, 15, and 60 minutes. If there aren't any in those intervals, the alert isn't shown. |=== == Technical Considerations @@ -396,4 +396,4 @@ a| Type of tasks the scheduler runs: * Use DIAF for initial troubleshooting before collecting heap or thread dumps manually. * Correlate events in the event dump section with logs by using the `eventId` for deeper analysis. -* Collect schedule diagnostics during maintenance windows in production environments. +* Collect scheduled diagnostics during maintenance windows in production environments. \ No newline at end of file From e3e191e5b70c385e117c5456f9a3d227c622a108 Mon Sep 17 00:00:00 2001 From: Daniela Merlo Date: Wed, 10 Sep 2025 18:25:22 -0300 Subject: [PATCH 08/33] W-19435968-XMLtoConfigure-TLS-410-dm --- modules/ROOT/pages/tls-configuration.adoc | 3 +++ 1 file changed, 3 insertions(+) diff --git a/modules/ROOT/pages/tls-configuration.adoc b/modules/ROOT/pages/tls-configuration.adoc index 0b818ca90..3567362aa 100644 --- a/modules/ROOT/pages/tls-configuration.adoc +++ b/modules/ROOT/pages/tls-configuration.adoc @@ -309,6 +309,9 @@ The attributes other than `path` are optional. | `algorithm` | The algorithm used in the keystore. Default is `SunX509`. |=== +[NOTE] +By default, the `path` attribute loads trust and keystore files as classloader resources. For on-premises deployments, set the system property `mule.tlsStores.filesystemLookup.enable` to `true` to enable file system access. + === Use Design Center to Configure TLS You can configure TLS for your app in Design Center. For example, to configure TLS in HTTP Listener: From e8aa84aff7a375dbea0291cb5f5099959056b2af Mon Sep 17 00:00:00 2001 From: Daniela Merlo <97902112+dmerlob@users.noreply.github.com> Date: Thu, 11 Sep 2025 10:27:08 -0300 Subject: [PATCH 09/33] Update modules/ROOT/pages/mule-troubleshooting-plugin.adoc Co-authored-by: Kevin Troller --- modules/ROOT/pages/mule-troubleshooting-plugin.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/ROOT/pages/mule-troubleshooting-plugin.adoc b/modules/ROOT/pages/mule-troubleshooting-plugin.adoc index 0f88e86c6..7a7dd65af 100644 --- a/modules/ROOT/pages/mule-troubleshooting-plugin.adoc +++ b/modules/ROOT/pages/mule-troubleshooting-plugin.adoc @@ -62,7 +62,7 @@ Output: The ZIP file is saved to the 'logs' directory by default. ---- -== Diagnostic Information Analysis File (DIAF) Contents +== Understanding Diagnostic Information Analysis File (DIAF) Contents The Diagnostic Information Analysis File (DIAF) groups all diagnostic data collected by the Mule Troubleshooting plugin into structured sections. Use this reference to understand the content of each section: From 7af735c52a9db1ce4bdd17e7dcb9b30d1470d438 Mon Sep 17 00:00:00 2001 From: Daniela Merlo <97902112+dmerlob@users.noreply.github.com> Date: Thu, 11 Sep 2025 10:28:37 -0300 Subject: [PATCH 10/33] Update modules/ROOT/pages/mule-troubleshooting-plugin.adoc --- modules/ROOT/pages/mule-troubleshooting-plugin.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/ROOT/pages/mule-troubleshooting-plugin.adoc b/modules/ROOT/pages/mule-troubleshooting-plugin.adoc index 7a7dd65af..fc49e2ba8 100644 --- a/modules/ROOT/pages/mule-troubleshooting-plugin.adoc +++ b/modules/ROOT/pages/mule-troubleshooting-plugin.adoc @@ -62,7 +62,7 @@ Output: The ZIP file is saved to the 'logs' directory by default. ---- -== Understanding Diagnostic Information Analysis File (DIAF) Contents +== Understanding Diagnostic Information Analysis File (DIAF) The Diagnostic Information Analysis File (DIAF) groups all diagnostic data collected by the Mule Troubleshooting plugin into structured sections. Use this reference to understand the content of each section: From 7a40f91b1d7489c9d8f85f3921874e95c3f608c7 Mon Sep 17 00:00:00 2001 From: Daniela Merlo <97902112+dmerlob@users.noreply.github.com> Date: Thu, 11 Sep 2025 11:15:38 -0300 Subject: [PATCH 11/33] Update modules/ROOT/pages/tls-configuration.adoc --- modules/ROOT/pages/tls-configuration.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/ROOT/pages/tls-configuration.adoc b/modules/ROOT/pages/tls-configuration.adoc index 3567362aa..dd14a68c0 100644 --- a/modules/ROOT/pages/tls-configuration.adoc +++ b/modules/ROOT/pages/tls-configuration.adoc @@ -310,7 +310,7 @@ The attributes other than `path` are optional. |=== [NOTE] -By default, the `path` attribute loads trust and keystore files as classloader resources. For on-premises deployments, set the system property `mule.tlsStores.filesystemLookup.enable` to `true` to enable file system access. +By default, the `path` attribute loads trust and keystore files as classloader resources. For on-premises deployments (hybrid or standalone), set the system property `mule.tlsStores.filesystemLookup.enable` to `true` to enable file system access. === Use Design Center to Configure TLS From 52552e939ca0e22aa2025c8e127216e1098c7931 Mon Sep 17 00:00:00 2001 From: Daniela Merlo Date: Thu, 11 Sep 2025 13:24:44 -0300 Subject: [PATCH 12/33] W-19615888-upgradeTOOL-BeforeUbegin-410-dm --- modules/ROOT/pages/_partials/upgrade-tool.adoc | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/modules/ROOT/pages/_partials/upgrade-tool.adoc b/modules/ROOT/pages/_partials/upgrade-tool.adoc index 9f197e1ba..baca6a3b6 100644 --- a/modules/ROOT/pages/_partials/upgrade-tool.adoc +++ b/modules/ROOT/pages/_partials/upgrade-tool.adoc @@ -1,5 +1,5 @@ //This content is reused in: -//mule-upgrade-tool.adoc +//mule-upgrade-tool.adoc under the Before You Begin section and Upgrading Clustered Mule Instances section. // Before You Begin // tag::BeforeYouBegin[] @@ -18,6 +18,9 @@ Download Mule runtime distributions from the https://help.mulesoft.com/s/[Help C * At least 2 GB of available disk space on the file system and access privileges to install the new Mule distribution. * (For Windows environments) The execution policy for Powershell scripts set to *Unrestricted*. * If Anypoint Monitoring agent is installed, uninstall it prior to the upgrade. +* Rename the `$MULE_HOME` directory before running the upgrade tool to use a generic name or one that matches the target version. For example, `mule-enterprise-4.9.8`. ++ +Renaming the directory after running the upgrade tool causes Anypoint Monitoring to stop working. To restore Anypoint Monitoring, uninstall and reinstall it. Alternatively, you can leave the directory name unchanged. // end::BeforeYouBegin[] // Upgrade Or Update Mule From 2d0122cd4c24cbdc29b381c47ae382ebb9439e87 Mon Sep 17 00:00:00 2001 From: Daniela Merlo Date: Thu, 11 Sep 2025 16:21:27 -0300 Subject: [PATCH 13/33] W-19449986-3erPARTYsoftware-410-dm --- .../pages/third-party-software-in-mule.adoc | 675 ++++++++++++------ 1 file changed, 444 insertions(+), 231 deletions(-) diff --git a/modules/ROOT/pages/third-party-software-in-mule.adoc b/modules/ROOT/pages/third-party-software-in-mule.adoc index 35abbabf7..9cd159851 100644 --- a/modules/ROOT/pages/third-party-software-in-mule.adoc +++ b/modules/ROOT/pages/third-party-software-in-mule.adoc @@ -13,237 +13,450 @@ The following table lists third-party software in Mule sorted by software compon [%header,cols="30,70"] |=== |License |Component -| Apache-2.0 | com.beust : jcommander : 1.82 -| Apache-2.0 | com.conversantmedia : disruptor : 1.2.21 -| Apache-2.0 | com.damnhandy : handy-uri-templates : 2.1.8 -| Apache-2.0 | com.fasterxml : aalto-xml : 1.3.2 -| Apache-2.0 | com.fasterxml.jackson.core : jackson-annotations : 2.16.1 -| Apache-2.0 | com.fasterxml.jackson.core : jackson-annotations : 2.18.2 -| Apache-2.0 | com.fasterxml.jackson.core : jackson-core : 2.16.1 -| Apache-2.0 | com.fasterxml.jackson.core : jackson-core : 2.18.2 -| Apache-2.0 | com.fasterxml.jackson.core : jackson-databind : 2.16.1 -| Apache-2.0 | com.fasterxml.jackson.core : jackson-databind : 2.18.2 -| Apache-2.0 | com.fasterxml.jackson.dataformat : jackson-dataformat-yaml : 2.18.2 -| Apache-2.0 | com.fasterxml.jackson.module : jackson-module-jsonschema : 2.18.2 -| Apache-2.0 | com.fasterxml.woodstox : woodstox-core : 6.6.1 -| Apache-2.0 | com.github.ben-manes.caffeine : caffeine : 2.9.3 -| Apache-2.0 | com.github.ben-manes.caffeine : caffeine : 3.1.8 -| Apache-2.0 | com.github.erosb : everit-json-schema : 1.14.3 -| Apache-2.0 | com.github.fge : btf : 1.2 -| Apache-2.0 | com.github.fge : msg-simple : 1.1 -| Apache-2.0 | com.github.fge : uri-template : 0.9 -| Apache-2.0 | com.github.java-json-tools : jackson-coreutils : 1.9 -| Apache-2.0 | com.github.java-json-tools : json-schema-core : 1.2.10 -| Apache-2.0 | com.github.java-json-tools : json-schema-validator : 2.2.10 -| Apache-2.0 | com.google.code.gson : gson : 2.11.0 -| Apache-2.0 | com.google.errorprone : error_prone_annotations : 2.10.0 -| Apache-2.0 | com.google.errorprone : error_prone_annotations : 2.36.0 -| Apache-2.0 | com.google.guava : failureaccess : 1.0.2 -| Apache-2.0 | com.google.guava : guava : 33.3.1-jre -| Apache-2.0 | com.google.guava : listenablefuture : 9999.0-empty-to-avoid-conflict-with-guava -| Apache-2.0 | com.google.j2objc : j2objc-annotations : 3.0.0 -| Apache-2.0 | com.googlecode.libphonenumber : libphonenumber : 8.0.0 -| Apache-2.0 | com.lmax : disruptor : 4.0.0 -| Apache-2.0 | com.squareup.okhttp3 : okhttp : 4.12.0 -| Apache-2.0 | com.squareup.okio : okio-jvm : 3.9.1 -| Apache-2.0 | com.typesafe : config : 1.4.3 -| Apache-2.0 | com.zaxxer : hikaricp-java7 : 2.4.13 -| Apache-2.0 | commons-beanutils : commons-beanutils : 1.9.4 -| Apache-2.0 | commons-cli : commons-cli : 1.9.0 -| Apache-2.0 | commons-codec : commons-codec : 1.17.0 -| Apache-2.0 | commons-codec : commons-codec : 1.17.1 -| Apache-2.0 | commons-collections : commons-collections : 3.2.2 -| Apache-2.0 | commons-digester : commons-digester : 2.1 -| Apache-2.0 | commons-io : commons-io : 2.16.1 -| Apache-2.0 | commons-io : commons-io : 2.18.0 -| Apache-2.0 | commons-lang : commons-lang : 2.6 -| Apache-2.0 | commons-net : commons-net : 3.11.1 -| Apache-2.0 | commons-validator : commons-validator : 1.7 -| Apache-2.0 | io.grpc : grpc-api : 1.68.2 -| Apache-2.0 | io.grpc : grpc-context : 1.68.2 -| Apache-2.0 | io.grpc : grpc-core : 1.68.2 -| Apache-2.0 | io.micrometer : micrometer-commons : 1.14.1 -| Apache-2.0 | io.micrometer : micrometer-observation : 1.14.1 -| Apache-2.0 | io.netty : netty-buffer : 4.1.115.final -| Apache-2.0 | io.netty : netty-codec : 4.1.115.final -| Apache-2.0 | io.netty : netty-codec-dns : 4.1.115.final -| Apache-2.0 | io.netty : netty-codec-http : 4.1.115.final -| Apache-2.0 | io.netty : netty-codec-http2 : 4.1.115.final -| Apache-2.0 | io.netty : netty-codec-socks : 4.1.115.final -| Apache-2.0 | io.netty : netty-common : 4.1.115.final -| Apache-2.0 | io.netty : netty-handler : 4.1.115.final -| Apache-2.0 | io.netty : netty-handler-proxy : 4.1.115.final -| Apache-2.0 | io.netty : netty-resolver : 4.1.115.final -| Apache-2.0 | io.netty : netty-resolver-dns : 4.1.115.final -| Apache-2.0 | io.netty : netty-transport : 4.1.115.final -| Apache-2.0 | io.netty : netty-transport-classes-epoll : 4.1.115.final -| Apache-2.0 | io.netty : netty-transport-native-epoll : jar : linux-x86_64 : 4.1.115.final -| Apache-2.0 | io.netty : netty-transport-native-unix-common : 4.1.115.final -| Apache-2.0 | io.opentelemetry : opentelemetry-api : 1.44.1 -| Apache-2.0 | io.opentelemetry : opentelemetry-api-incubator : 1.44.1-alpha -| Apache-2.0 | io.opentelemetry : opentelemetry-context : 1.44.1 -| Apache-2.0 | io.opentelemetry : opentelemetry-exporter-common : 1.44.1 -| Apache-2.0 | io.opentelemetry : opentelemetry-exporter-logging : 1.44.1 -| Apache-2.0 | io.opentelemetry : opentelemetry-exporter-otlp : 1.44.1 -| Apache-2.0 | io.opentelemetry : opentelemetry-exporter-otlp-common : 1.44.1 -| Apache-2.0 | io.opentelemetry : opentelemetry-exporter-sender-okhttp : 1.44.1 -| Apache-2.0 | io.opentelemetry : opentelemetry-sdk : 1.44.1 -| Apache-2.0 | io.opentelemetry : opentelemetry-sdk-common : 1.44.1 -| Apache-2.0 | io.opentelemetry : opentelemetry-sdk-extension-autoconfigure-spi : 1.44.1 -| Apache-2.0 | io.opentelemetry : opentelemetry-sdk-logs : 1.44.1 -| Apache-2.0 | io.opentelemetry : opentelemetry-sdk-metrics : 1.44.1 -| Apache-2.0 | io.opentelemetry : opentelemetry-sdk-testing : 1.44.1 -| Apache-2.0 | io.opentelemetry : opentelemetry-sdk-trace : 1.44.1 -| Apache-2.0 | io.perfmark : perfmark-api : 0.27.0 -| Apache-2.0 | io.projectreactor : reactor-core : 3.7.0 -| Apache-2.0 | io.projectreactor.addons : reactor-extra : 3.5.2 -| Apache-2.0 | io.projectreactor.netty : reactor-netty-core : 1.2.0 -| Apache-2.0 | io.projectreactor.netty : reactor-netty-http : 1.2.0 -| Apache-2.0 | io.qameta.allure : allure-java-commons : 2.29.1 -| Apache-2.0 | io.qameta.allure : allure-junit4 : 2.29.1 -| Apache-2.0 | io.qameta.allure : allure-model : 2.29.1 -| Apache-2.0 | io.qameta.allure : allure-test-filter : 2.29.1 -| Apache-2.0 | it.unimi.dsi : fastutil : 8.5.15 -| Apache-2.0 | jakarta.inject : jakarta.inject-api : 1.0.5 -| Apache-2.0 | javax.validation : validation-api : 1.1.0.final -| Apache-2.0 | joda-time : joda-time : 2.10.2 -| Apache-2.0 | joda-time : joda-time : 2.13.0 -| Apache-2.0 | net.bytebuddy : byte-buddy : 1.15.10 -| Apache-2.0 | net.bytebuddy : byte-buddy-agent : 1.15.10 -| Apache-2.0 | net.jodah : failsafe : 2.4.4 -| Apache-2.0 | net.lingala.zip4j : zip4j : 2.11.3 -| Apache-2.0 | org.apache.avro : avro : 1.11.4 -| Apache-2.0 | org.apache.commons : commons-collections4 : 4.4 -| Apache-2.0 | org.apache.commons : commons-compress : 1.26.2 -| Apache-2.0 | org.apache.commons : commons-exec : 1.4.0 -| Apache-2.0 | org.apache.commons : commons-lang3 : 3.14.0 -| Apache-2.0 | org.apache.commons : commons-lang3 : 3.17.0 -| Apache-2.0 | org.apache.commons : commons-pool2 : 2.12.0 -| Apache-2.0 | org.apache.commons : commons-text : 1.12.0 -| Apache-2.0 | org.apache.derby : derby : 10.16.1.1 -| Apache-2.0 | org.apache.ftpserver : ftplet-api : 1.2.0 -| Apache-2.0 | org.apache.ftpserver : ftpserver-core : 1.2.0 -| Apache-2.0 | org.apache.groovy : groovy : 4.0.24 -| Apache-2.0 | org.apache.httpcomponents : httpclient : 4.5.14 -| Apache-2.0 | org.apache.httpcomponents : httpcore : 4.4.16 -| Apache-2.0 | org.apache.logging.log4j : log4j-1.2-api : 2.24.2 -| Apache-2.0 | org.apache.logging.log4j : log4j-api : 2.24.2 -| Apache-2.0 | org.apache.logging.log4j : log4j-core : 2.24.2 -| Apache-2.0 | org.apache.logging.log4j : log4j-slf4j2-impl : 2.24.2 -| Apache-2.0 | org.apache.maven : maven-builder-support : 3.9.9 -| Apache-2.0 | org.apache.maven : maven-model-builder : 3.9.9 -| Apache-2.0 | org.apache.maven : maven-resolver-provider : 3.9.9 -| Apache-2.0 | org.apache.maven : maven-settings : 3.9.9 -| Apache-2.0 | org.apache.maven : maven-settings-builder : 3.9.9 -| Apache-2.0 | org.apache.maven.resolver : maven-resolver-api : 1.9.18 -| Apache-2.0 | org.apache.maven.resolver : maven-resolver-connector-basic : 1.9.18 -| Apache-2.0 | org.apache.maven.resolver : maven-resolver-impl : 1.9.18 -| Apache-2.0 | org.apache.maven.resolver : maven-resolver-named-locks : 1.9.18 -| Apache-2.0 | org.apache.maven.resolver : maven-resolver-spi : 1.9.18 -| Apache-2.0 | org.apache.maven.resolver : maven-resolver-supplier : 1.9.18 -| Apache-2.0 | org.apache.maven.resolver : maven-resolver-transport-file : 1.9.18 -| Apache-2.0 | org.apache.maven.resolver : maven-resolver-transport-http : 1.9.18 -| Apache-2.0 | org.apache.maven.resolver : maven-resolver-transport-wagon : 1.9.18 -| Apache-2.0 | org.apache.maven.resolver : maven-resolver-util : 1.9.18 -| Apache-2.0 | org.apache.maven.shared : maven-invoker : 3.3.0 -| Apache-2.0 | org.apache.maven.shared : maven-shared-utils : 3.4.2 -| Apache-2.0 | org.apache.maven.wagon : wagon-http : 3.5.3 -| Apache-2.0 | org.apache.maven.wagon : wagon-http-shared : 3.5.3 -| Apache-2.0 | org.apache.maven.wagon : wagon-provider-api : 3.5.3 -| Apache-2.0 | org.apache.mina : mina-core : 2.1.6 -| Apache-2.0 | org.apache.sshd : sshd-osgi : 2.14.0 -| Apache-2.0 | org.apache.sshd : sshd-scp : 2.14.0 -| Apache-2.0 | org.apache.sshd : sshd-sftp : 2.14.0 -| Apache-2.0 | org.apache.ws.xmlschema : xmlschema-core : 2.2.1 -| Apache-2.0 | org.apache.xmlbeans : xmlbeans : 3.1.0 -| Apache-2.0 | org.apache.xmlbeans : xmlbeans : 5.2.2 -| Apache-2.0 | org.awaitility : awaitility : 4.2.2 -| Apache-2.0 | org.codehaus.plexus : plexus-cipher : 2.0 -| Apache-2.0 | org.codehaus.plexus : plexus-component-annotations : 2.2.0 -| Apache-2.0 | org.codehaus.plexus : plexus-interpolation : 1.27 -| Apache-2.0 | org.codehaus.plexus : plexus-sec-dispatcher : 2.0 -| Apache-2.0 | org.codehaus.plexus : plexus-utils : 4.0.2 -| Apache-2.0 | org.codehaus.plexus : plexus-xml : 3.0.1 -| Apache-2.0 | org.jetbrains : annotations : 26.0.1 -| Apache-2.0 | org.jetbrains.kotlin : kotlin-stdlib : 2.1.0 -| Apache-2.0 | org.jetbrains.kotlin : kotlin-stdlib-jdk7 : 2.1.0 -| Apache-2.0 | org.jetbrains.kotlin : kotlin-stdlib-jdk8 : 2.1.0 -| Apache-2.0 | org.jheaps : jheaps : 0.14 -| Apache-2.0 | org.objenesis : objenesis : 3.3 -| Apache-2.0 | org.parboiled : parboiled_2.12 : 2.5.1 -| Apache-2.0 | org.quartz-scheduler : quartz : 2.3.2 -| Apache-2.0 | org.raml : raml-parser-2 : 1.0.44-15 -| Apache-2.0 | org.raml : yagi : 1.0.44-15 -| Apache-2.0 | org.reflections : reflections : 0.10.2 -| Apache-2.0 | org.scala-lang : scala-library : 2.12.18 -| Apache-2.0 | org.slf4j : jcl-over-slf4j : 2.0.16 -| Apache-2.0 | org.springframework : spring-aop : 6.2.0 -| Apache-2.0 | org.springframework : spring-beans : 6.2.0 -| Apache-2.0 | org.springframework : spring-context : 6.2.0 -| Apache-2.0 | org.springframework : spring-core : 6.2.0 -| Apache-2.0 | org.springframework : spring-expression : 6.2.0 -| Apache-2.0 | org.togglz : togglz-core : 4.4.0 -| Apache-2.0 | org.vibur : vibur-object-pool : 25.0 -| Apache-2.0 | org.yaml : snakeyaml : 2.3 -| BSD-2-Clause | org.codehaus.woodstox : stax2-api : 4.2.2 -| BSD-3-Clause | com.google.re2j : re2j : 1.6 -| BSD-3-Clause | com.google.re2j : re2j : 1.7 -| BSD-3-Clause | org.antlr : antlr-runtime : 3.5.3 -| BSD-3-Clause | org.hamcrest : hamcrest : 3.0 -| CDDL-1.1 | org.glassfish.grizzly : grizzly-http : 2.3.34 -| CDDL-1.1 | org.glassfish.grizzly : grizzly-http-server : 2.3.34 -| CDDL-1.1 | org.glassfish.grizzly : grizzly-http-servlet : 2.3.34 -| CDDL-1.1 | org.glassfish.grizzly : grizzly-websockets : 2.4.0-beta4 -| DOM4j-License | org.dom4j : dom4j : 2.1.4 -| EDL-1.0 | com.sun.activation : jakarta.activation : 1.2.1 -| EDL-1.0 | com.sun.activation : jakarta.activation : 1.2.2 -| EDL-1.0 | com.sun.mail : jakarta.mail : 1.6.3 -| EDL-1.0 | com.sun.mail : jakarta.mail : 1.6.7 -| EDL-1.0 | com.sun.xml.bind : jaxb-impl : 2.3.9 -| EDL-1.0 | jakarta.xml.bind : jakarta.xml.bind-api : 2.3.3 -| EPL-1.0 | com.mchange : c3p0 : 0.10.1 -| EPL-1.0 | com.mchange : mchange-commons-java : 0.3.1 -| EPL-1.0 | junit : junit : 4.13.2 -| EPL-1.0 | org.eclipse.sisu : org.eclipse.sisu.inject : 0.3.5 -| EPL-1.0 | org.eclipse.sisu : org.eclipse.sisu.plexus : 0.3.5 -| EPL-2.0 | jakarta.annotation : jakarta.annotation-api : 1.3.5 -| EPL-2.0 | jakarta.jms : jakarta.jms-api : 2.0.3 -| EPL-2.0 | jakarta.transaction : jakarta.transaction-api : 1.3.3 -| EPL-2.0 | org.aspectj : aspectjweaver : 1.9.22.1 -| EPL-2.0 | org.glassfish : jakarta.json : 1.1.6 -| EPL-2.0 | org.jgrapht : jgrapht-core : 1.5.2 -| ICU or Unicode | org.graalvm.shadowed : icu4j : 24.1.1 -| LGPL-2.1 | com.github.spotbugs : spotbugs-annotations : 4.7.3 -| MIT | com.vdurmont : semver4j : 3.1.0 -| MIT | net.sf.jopt-simple : jopt-simple : 5.0.3 -| MIT | org.apfloat : apfloat : 1.14.0 -| MIT | org.apfloat : apfloat : 1.14.0 -| MIT | org.checkerframework : checker-qual : 3.19.0 -| MIT | org.checkerframework : checker-qual : 3.48.3 -| MIT | org.graalvm.js : js : 23.0.6 -| MIT | org.graalvm.js js 1.0.0-rc15 -| MIT | org.jsoup : jsoup : 1.18.3 -| MIT | org.mockito : mockito-core : 4.11.0 -| MIT | org.slf4j : jul-to-slf4j : 2.0.16 -| MIT | org.slf4j : slf4j-api : 2.0.16 -| MIT | superstartup-closure-compiler 0.1.1 -| MIT | tanukisoft : wrapper : 3.2.3 -| MIT-0 | org.reactivestreams : reactive-streams : 1.0.4 -| MPL-1.1 | com.googlecode.juniversalchardet : juniversalchardet : 1.0.3 -| MPL-2.0 | org.mozilla : rhino : 1.7.15 -| Public Domain | org.json : json : 20231013 -| Public Domain | org.json : json : 20240303 -| Unicode-3.0 | com.ibm.icu : icu4j : 76.1 -| UPL-1.0 | org.graalvm.js : js-scriptengine : 24.1.1 -| UPL-1.0 | org.graalvm.polyglot : polyglot : 24.1.1 -| UPL-1.0 | org.graalvm.regex : regex : 24.1.1 -| UPL-1.0 | org.graalvm.sdk : collections : 24.1.1 -| UPL-1.0 | org.graalvm.sdk : graal-sdk : 24.1.1 -| UPL-1.0 | org.graalvm.sdk : graal-sdk : 24.1.1 -| UPL-1.0 | org.graalvm.sdk : graal-sdk : 24.1.1 -| UPL-1.0 | org.graalvm.sdk : nativeimage : 24.1.1 -| UPL-1.0 | org.graalvm.sdk : word : 24.1.1 -| UPL-1.0 | org.graalvm.truffle : truffle-api : 24.1.1 +|Apache-2.0 |com.amazonaws : aws-java-sdk-cloudwatch : 1.12.674 +|Apache-2.0 |com.amazonaws : aws-java-sdk-core : 1.12.674 +|Apache-2.0 |com.amazonaws : aws-java-sdk-pinpoint : 1.12.674 +|Apache-2.0 |com.amazonaws : jmespath-java : 1.12.674 +|Apache-2.0 |com.beust : jcommander : 1.82 +|Apache-2.0 |com.conversantmedia : disruptor : 1.2.21 +|Apache-2.0 |com.damnhandy : handy-uri-templates : 2.1.8 +|Apache-2.0 |com.esotericsoftware : kryo-shaded : 4.0.3 +|Apache-2.0 |com.esotericsoftware : kryo-shaded : 4.0.3 +|Apache-2.0 |com.fasterxml : aalto-xml : 1.3.2 +|Apache-2.0 |com.fasterxml.jackson.core : jackson-annotations : 2.16.0 +|Apache-2.0 |com.fasterxml.jackson.core : jackson-annotations : 2.17.2 +|Apache-2.0 |com.fasterxml.jackson.core : jackson-annotations : 2.19.2 +|Apache-2.0 |com.fasterxml.jackson.core : jackson-core : 2.16.0 +|Apache-2.0 |com.fasterxml.jackson.core : jackson-core : 2.17.2 +|Apache-2.0 |com.fasterxml.jackson.core : jackson-core : 2.19.2 +|Apache-2.0 |com.fasterxml.jackson.core : jackson-databind : 2.16.0 +|Apache-2.0 |com.fasterxml.jackson.core : jackson-databind : 2.17.2 +|Apache-2.0 |com.fasterxml.jackson.core : jackson-databind : 2.19.2 +|Apache-2.0 |com.fasterxml.jackson.dataformat : jackson-dataformat-cbor : 2.12.6 +|Apache-2.0 |com.fasterxml.jackson.dataformat : jackson-dataformat-yaml : 2.19.2 +|Apache-2.0 |com.fasterxml.jackson.datatype : jackson-datatype-jsr310 : 2.19.2 +|Apache-2.0 |com.fasterxml.jackson.module : jackson-module-jaxb-annotations : 2.14.1 +|Apache-2.0 |com.fasterxml.jackson.module : jackson-module-jsonschema : 2.19.2 +|Apache-2.0 |com.fasterxml.uuid : java-uuid-generator : 3.1.3 +|Apache-2.0 |com.fasterxml.woodstox : woodstox-core : 6.6.1 +|Apache-2.0 |com.fasterxml.woodstox : woodstox-core : 6.7.0 +|Apache-2.0 |com.github.ben-manes.caffeine : caffeine : 3.0.5 +|Apache-2.0 |com.github.ben-manes.caffeine : caffeine : 3.2.2 +|Apache-2.0 |com.github.erosb : everit-json-schema : 1.14.3 +|Apache-2.0 |com.github.fge : btf : 1.2 +|Apache-2.0 |com.github.fge : msg-simple : 1.1 +|Apache-2.0 |com.github.fge : uri-template : 0.9 +|Apache-2.0 |com.github.java-json-tools : jackson-coreutils : 1.9 +|Apache-2.0 |com.github.java-json-tools : json-schema-core : 1.2.10 +|Apache-2.0 |com.github.java-json-tools : json-schema-validator : 2.2.10 +|Apache-2.0 |com.github.jknack : handlebars : 4.3.1 +|Apache-2.0 |com.github.jknack : handlebars : 4.3.1 +|Apache-2.0 |com.github.jknack : handlebars-proto : 4.1.0 +|Apache-2.0 |com.github.jsendnsca : jsendnsca : 2.1.1 +|Apache-2.0 |com.github.pjfanning : excel-streaming-reader : 4.1.2 +|Apache-2.0 |com.github.pjfanning : poi-shared-strings : 2.6.1 +|Apache-2.0 |com.github.virtuald : curvesapi : 1.08 +|Apache-2.0 |com.google.code.findbugs : jsr305 : 3.0.2 +|Apache-2.0 |com.google.code.gson : gson : 2.12.1 +|Apache-2.0 |com.google.code.gson : gson : 2.13.1 +|Apache-2.0 |com.google.errorprone : error_prone_annotations : 2.10.0 +|Apache-2.0 |com.google.errorprone : error_prone_annotations : 2.18.0 +|Apache-2.0 |com.google.errorprone : error_prone_annotations : 2.36.0 +|Apache-2.0 |com.google.errorprone : error_prone_annotations : 2.41.0 +|Apache-2.0 |com.google.guava : failureaccess : 1.0.1 +|Apache-2.0 |com.google.guava : failureaccess : 1.0.2 +|Apache-2.0 |com.google.guava : guava : 32.0.1-jre +|Apache-2.0 |com.google.guava : guava : 33.3.1-jre +|Apache-2.0 |com.google.guava : guava : 33.4.0-jre +|Apache-2.0 |com.google.guava : listenablefuture : 9999.0-empty-to-avoid-conflict-with-guava +|Apache-2.0 |com.google.inject : guice : 5.0.1 +|Apache-2.0 |com.google.j2objc : j2objc-annotations : 2.8 +|Apache-2.0 |com.google.j2objc : j2objc-annotations : 3.0.0 +|Apache-2.0 |com.googlecode.libphonenumber : libphonenumber : 8.0.0 +|Apache-2.0 |com.hazelcast : hazelcast : 5.2.5 +|Apache-2.0 |com.lmax : disruptor : 3.4.3 +|Apache-2.0 |com.lmax : disruptor : 4.0.0 +|Apache-2.0 |com.netflix.servo : servo-core : 0.12.22 +|Apache-2.0 |com.netflix.spectator : spectator-api : 0.67.0 +|Apache-2.0 |com.splunk : splunk : 1.6.4.0 +|Apache-2.0 |com.squareup : tape : 1.2.2 +|Apache-2.0 |com.squareup.okhttp3 : logging-interceptor : 4.11.0 +|Apache-2.0 |com.squareup.okhttp3 : okhttp : 4.11.0 +|Apache-2.0 |com.squareup.okhttp3 : okhttp : 4.12.0 +|Apache-2.0 |com.squareup.okio : okio : 3.4.0 +|Apache-2.0 |com.squareup.okio : okio-jvm : 3.16.0 +|Apache-2.0 |com.squareup.okio : okio-jvm : 3.4.0 +|Apache-2.0 |com.typesafe : config : 1.4.4 +|Apache-2.0 |com.typesafe.netty : netty-reactive-streams : 2.0.4 +|Apache-2.0 |com.zaxxer : sparsebitset : 1.3 +|Apache-2.0 |commons-beanutils : commons-beanutils : 1.11.0 +|Apache-2.0 |commons-cli : commons-cli : 1.10.0 +|Apache-2.0 |commons-cli : commons-cli : 1.4 +|Apache-2.0 |commons-codec : commons-codec : 1.14 +|Apache-2.0 |commons-codec : commons-codec : 1.17.1 +|Apache-2.0 |commons-codec : commons-codec : 1.19.0 +|Apache-2.0 |commons-collections : commons-collections : 3.2.2 +|Apache-2.0 |commons-dbutils : commons-dbutils : 1.8.1 +|Apache-2.0 |commons-digester : commons-digester : 2.1 +|Apache-2.0 |commons-io : commons-io : 2.15.0 +|Apache-2.0 |commons-io : commons-io : 2.18.0 +|Apache-2.0 |commons-io : commons-io : 2.20.0 +|Apache-2.0 |commons-lang : commons-lang : 2.4 +|Apache-2.0 |commons-lang : commons-lang : 2.6 +|Apache-2.0 |commons-logging : commons-logging : 1.2 +|Apache-2.0 |commons-validator : commons-validator : 1.7 +|Apache-2.0 |de.javakaffee : kryo-serializers : 0.45 +|Apache-2.0 |io.dropwizard.metrics : metrics-core : 3.1.5 +|Apache-2.0 |io.grpc : grpc-api : 1.74.0 +|Apache-2.0 |io.grpc : grpc-context : 1.74.0 +|Apache-2.0 |io.grpc : grpc-core : 1.74.0 +|Apache-2.0 |io.jsonwebtoken : jjwt-api : 0.11.5 +|Apache-2.0 |io.jsonwebtoken : jjwt-gson : 0.11.5 +|Apache-2.0 |io.jsonwebtoken : jjwt-impl : 0.11.5 +|Apache-2.0 |io.keploy : test-module : 1.0.5 +|Apache-2.0 |io.micrometer : micrometer-commons : 1.14.1 +|Apache-2.0 |io.micrometer : micrometer-commons : 1.15.2 +|Apache-2.0 |io.micrometer : micrometer-observation : 1.14.1 +|Apache-2.0 |io.micrometer : micrometer-observation : 1.15.2 +|Apache-2.0 |io.netty : netty-buffer : 4.1.118.final +|Apache-2.0 |io.netty : netty-buffer : 4.1.124.final +|Apache-2.0 |io.netty : netty-codec : 4.1.118.final +|Apache-2.0 |io.netty : netty-codec : 4.1.124.final +|Apache-2.0 |io.netty : netty-codec-dns : 4.1.124.final +|Apache-2.0 |io.netty : netty-codec-http : 4.1.118.final +|Apache-2.0 |io.netty : netty-codec-http : 4.1.124.final +|Apache-2.0 |io.netty : netty-codec-http2 : 4.1.124.final +|Apache-2.0 |io.netty : netty-codec-socks : 4.1.118.final +|Apache-2.0 |io.netty : netty-codec-socks : 4.1.124.final +|Apache-2.0 |io.netty : netty-common : 4.1.118.final +|Apache-2.0 |io.netty : netty-common : 4.1.124.final +|Apache-2.0 |io.netty : netty-handler : 4.1.118.final +|Apache-2.0 |io.netty : netty-handler : 4.1.124.final +|Apache-2.0 |io.netty : netty-handler-proxy : 4.1.118.final +|Apache-2.0 |io.netty : netty-handler-proxy : 4.1.124.final +|Apache-2.0 |io.netty : netty-resolver : 4.1.118.final +|Apache-2.0 |io.netty : netty-resolver : 4.1.124.final +|Apache-2.0 |io.netty : netty-resolver-dns : 4.1.124.final +|Apache-2.0 |io.netty : netty-transport : 4.1.118.final +|Apache-2.0 |io.netty : netty-transport : 4.1.124.final +|Apache-2.0 |io.netty : netty-transport-classes-epoll : 4.1.118.final +|Apache-2.0 |io.netty : netty-transport-classes-epoll : 4.1.124.final +|Apache-2.0 |io.netty : netty-transport-native-epoll : 4.1.124.final +|Apache-2.0 |io.netty : netty-transport-native-epoll : jar : linux-x86_64 : 4.1.118.final +|Apache-2.0 |io.netty : netty-transport-native-epoll : jar : linux-x86_64 : 4.1.124.final +|Apache-2.0 |io.netty : netty-transport-native-unix-common : 4.1.118.final +|Apache-2.0 |io.netty : netty-transport-native-unix-common : 4.1.124.final +|Apache-2.0 |io.opentelemetry : opentelemetry-api : 1.49.0 +|Apache-2.0 |io.opentelemetry : opentelemetry-context : 1.49.0 +|Apache-2.0 |io.opentelemetry : opentelemetry-exporter-common : 1.49.0 +|Apache-2.0 |io.opentelemetry : opentelemetry-exporter-otlp : 1.49.0 +|Apache-2.0 |io.opentelemetry : opentelemetry-exporter-otlp-common : 1.49.0 +|Apache-2.0 |io.opentelemetry : opentelemetry-exporter-sender-okhttp : 1.49.0 +|Apache-2.0 |io.opentelemetry : opentelemetry-sdk : 1.49.0 +|Apache-2.0 |io.opentelemetry : opentelemetry-sdk-common : 1.49.0 +|Apache-2.0 |io.opentelemetry : opentelemetry-sdk-extension-autoconfigure-spi : 1.49.0 +|Apache-2.0 |io.opentelemetry : opentelemetry-sdk-logs : 1.49.0 +|Apache-2.0 |io.opentelemetry : opentelemetry-sdk-metrics : 1.49.0 +|Apache-2.0 |io.opentelemetry : opentelemetry-sdk-trace : 1.49.0 +|Apache-2.0 |io.opentelemetry.instrumentation : opentelemetry-instrumentation-api : 2.15.0 +|Apache-2.0 |io.opentelemetry.instrumentation : opentelemetry-log4j-appender-2.17 : 2.15.0-alpha +|Apache-2.0 |io.opentelemetry.instrumentation : opentelemetry-log4j-context-data-2.17-autoconfigure : 2.15.0-alpha +|Apache-2.0 |io.opentelemetry.semconv : opentelemetry-semconv : 1.32.0 +|Apache-2.0 |io.perfmark : perfmark-api : 0.27.0 +|Apache-2.0 |io.projectreactor : reactor-core : 3.7.8 +|Apache-2.0 |io.projectreactor.addons : reactor-extra : 3.5.2 +|Apache-2.0 |io.projectreactor.netty : reactor-netty-core : 1.2.8 +|Apache-2.0 |io.projectreactor.netty : reactor-netty-http : 1.2.8 +|Apache-2.0 |io.qameta.allure : allure-java-commons : 2.29.1 +|Apache-2.0 |io.qameta.allure : allure-junit-platform : 2.29.1 +|Apache-2.0 |io.qameta.allure : allure-junit5 : 2.29.1 +|Apache-2.0 |io.qameta.allure : allure-model : 2.29.1 +|Apache-2.0 |io.qameta.allure : allure-test-filter : 2.29.1 +|Apache-2.0 |it.unimi.dsi : fastutil : 8.5.16 +|Apache-2.0 |jakarta.enterprise : jakarta.enterprise.cdi-api : 3.0.1 +|Apache-2.0 |jakarta.inject : jakarta.inject-api : 1.0.5 +|Apache-2.0 |jakarta.inject : jakarta.inject-api : 2.0.1 +|Apache-2.0 |jakarta.validation : jakarta.validation-api : 2.0.2 +|Apache-2.0 |javax.inject : javax.inject : 1 +|Apache-2.0 |javax.validation : validation-api : 1.0.0.ga +|Apache-2.0 |javax.validation : validation-api : 1.1.0.final +|Apache-2.0 |joda-time : joda-time : 2.10.2 +|Apache-2.0 |joda-time : joda-time : 2.13.0 +|Apache-2.0 |joda-time : joda-time : 2.14.0 +|Apache-2.0 |joda-time : joda-time : 2.9.1 +|Apache-2.0 |net.bytebuddy : byte-buddy : 1.17.6 +|Apache-2.0 |net.java.dev.jna : jna : 5.15.0 +|Apache-2.0 |net.java.dev.jna : jna-platform : 5.15.0 +|Apache-2.0 |net.jodah : failsafe : 2.4.4 +|Apache-2.0 |net.sf.saxon : saxon-he : 12.5 +|Apache-2.0 |net.shibboleth.utilities : java-support : 7.5.2 +|Apache-2.0 |org.apache.avro : avro : 1.12.0 +|Apache-2.0 |org.apache.commons : commons-collections4 : 4.4 +|Apache-2.0 |org.apache.commons : commons-collections4 : 4.5.0 +|Apache-2.0 |org.apache.commons : commons-compress : 1.27.1 +|Apache-2.0 |org.apache.commons : commons-compress : 1.28.0 +|Apache-2.0 |org.apache.commons : commons-lang3 : 3.14.0 +|Apache-2.0 |org.apache.commons : commons-lang3 : 3.16.0 +|Apache-2.0 |org.apache.commons : commons-lang3 : 3.17.0 +|Apache-2.0 |org.apache.commons : commons-lang3 : 3.18.0 +|Apache-2.0 |org.apache.commons : commons-math3 : 3.6.1 +|Apache-2.0 |org.apache.commons : commons-pool2 : 2.12.1 +|Apache-2.0 |org.apache.commons : commons-text : 1.10.0 +|Apache-2.0 |org.apache.commons : commons-text : 1.14.0 +|Apache-2.0 |org.apache.cxf : cxf-core : 3.5.9 +|Apache-2.0 |org.apache.cxf : cxf-rt-bindings-soap : 3.5.9 +|Apache-2.0 |org.apache.cxf : cxf-rt-databinding-jaxb : 3.5.9 +|Apache-2.0 |org.apache.cxf : cxf-rt-frontend-simple : 3.5.9 +|Apache-2.0 |org.apache.cxf : cxf-rt-management : 3.5.9 +|Apache-2.0 |org.apache.cxf : cxf-rt-security : 3.5.9 +|Apache-2.0 |org.apache.cxf : cxf-rt-security-saml : 3.5.9 +|Apache-2.0 |org.apache.cxf : cxf-rt-ws-addr : 3.5.9 +|Apache-2.0 |org.apache.cxf : cxf-rt-ws-policy : 3.5.9 +|Apache-2.0 |org.apache.cxf : cxf-rt-ws-rm : 3.5.9 +|Apache-2.0 |org.apache.cxf : cxf-rt-ws-security : 3.5.9 +|Apache-2.0 |org.apache.cxf : cxf-rt-wsdl : 3.5.9 +|Apache-2.0 |org.apache.httpcomponents : fluent-hc : 4.5.14 +|Apache-2.0 |org.apache.httpcomponents : httpclient : 4.5.13 +|Apache-2.0 |org.apache.httpcomponents : httpclient : 4.5.14 +|Apache-2.0 |org.apache.httpcomponents : httpcore : 4.4.16 +|Apache-2.0 |org.apache.httpcomponents : httpcore : 4.4.5 +|Apache-2.0 |org.apache.httpcomponents.client5 : httpclient5 : 5.1.3 +|Apache-2.0 |org.apache.httpcomponents.core5 : httpcore5 : 5.1.3 +|Apache-2.0 |org.apache.httpcomponents.core5 : httpcore5-h2 : 5.1.3 +|Apache-2.0 |org.apache.logging.log4j : log4j-1.2-api : 2.22.1 +|Apache-2.0 |org.apache.logging.log4j : log4j-1.2-api : 2.25.1 +|Apache-2.0 |org.apache.logging.log4j : log4j-api : 2.22.1 +|Apache-2.0 |org.apache.logging.log4j : log4j-api : 2.24.3 +|Apache-2.0 |org.apache.logging.log4j : log4j-api : 2.25.1 +|Apache-2.0 |org.apache.logging.log4j : log4j-core : +|Apache-2.0 |org.apache.logging.log4j : log4j-core : 2.25.1 +|Apache-2.0 |org.apache.logging.log4j : log4j-slf4j2-impl : 2.20.0 +|Apache-2.0 |org.apache.logging.log4j : log4j-slf4j2-impl : 2.25.1 +|Apache-2.0 |org.apache.maven : maven-artifact : 3.8.5 +|Apache-2.0 |org.apache.maven : maven-builder-support : 3.9.9 +|Apache-2.0 |org.apache.maven : maven-model-builder : 3.9.9 +|Apache-2.0 |org.apache.maven : maven-resolver-provider : 3.9.9 +|Apache-2.0 |org.apache.maven : maven-settings : 3.9.9 +|Apache-2.0 |org.apache.maven : maven-settings-builder : 3.9.9 +|Apache-2.0 |org.apache.maven.resolver : maven-resolver-api : 1.9.22 +|Apache-2.0 |org.apache.maven.resolver : maven-resolver-connector-basic : 1.9.22 +|Apache-2.0 |org.apache.maven.resolver : maven-resolver-impl : 1.9.22 +|Apache-2.0 |org.apache.maven.resolver : maven-resolver-named-locks : 1.9.22 +|Apache-2.0 |org.apache.maven.resolver : maven-resolver-spi : 1.9.22 +|Apache-2.0 |org.apache.maven.resolver : maven-resolver-supplier : 1.9.22 +|Apache-2.0 |org.apache.maven.resolver : maven-resolver-transport-file : 1.9.22 +|Apache-2.0 |org.apache.maven.resolver : maven-resolver-transport-http : 1.9.22 +|Apache-2.0 |org.apache.maven.resolver : maven-resolver-transport-wagon : 1.9.22 +|Apache-2.0 |org.apache.maven.resolver : maven-resolver-util : 1.9.22 +|Apache-2.0 |org.apache.maven.wagon : wagon-http : 3.5.3 +|Apache-2.0 |org.apache.maven.wagon : wagon-http-shared : 3.5.3 +|Apache-2.0 |org.apache.maven.wagon : wagon-provider-api : 3.5.3 +|Apache-2.0 |org.apache.neethi : neethi : 3.2.0 +|Apache-2.0 |org.apache.poi : poi : 5.4.0 +|Apache-2.0 |org.apache.poi : poi-ooxml : 5.4.0 +|Apache-2.0 |org.apache.poi : poi-ooxml-lite : 5.4.0 +|Apache-2.0 |org.apache.santuario : xmlsec : 2.3.4 +|Apache-2.0 |org.apache.velocity : velocity-engine-core : 2.4.1 +|Apache-2.0 |org.apache.ws.xmlschema : xmlschema-core : 2.2.1 +|Apache-2.0 |org.apache.wss4j : wss4j-bindings : 2.4.3 +|Apache-2.0 |org.apache.wss4j : wss4j-policy : 2.4.3 +|Apache-2.0 |org.apache.wss4j : wss4j-ws-security-common : 2.4.3 +|Apache-2.0 |org.apache.wss4j : wss4j-ws-security-dom : 2.4.3 +|Apache-2.0 |org.apache.wss4j : wss4j-ws-security-policy-stax : 2.4.3 +|Apache-2.0 |org.apache.wss4j : wss4j-ws-security-stax : 2.4.3 +|Apache-2.0 |org.apache.xmlbeans : xmlbeans : 5.3.0 +|Apache-2.0 |org.apiguardian : apiguardian-api : 1.1.2 +|Apache-2.0 |org.asynchttpclient : async-http-client : 2.12.4 +|Apache-2.0 |org.asynchttpclient : async-http-client-netty-utils : 2.12.4 +|Apache-2.0 |org.codehaus.plexus : plexus-cipher : 2.0 +|Apache-2.0 |org.codehaus.plexus : plexus-component-annotations : 2.1.0 +|Apache-2.0 |org.codehaus.plexus : plexus-interpolation : 1.27 +|Apache-2.0 |org.codehaus.plexus : plexus-sec-dispatcher : 2.0 +|Apache-2.0 |org.codehaus.plexus : plexus-utils : 3.3.0 +|Apache-2.0 |org.codehaus.plexus : plexus-utils : 3.5.1 +|Apache-2.0 |org.codehaus.woodstox : stax2-api : 4.2.2 +|Apache-2.0 |org.cryptacular : cryptacular : 1.2.6 +|Apache-2.0 |org.eclipse.jetty : jetty-client : 9.4.57.v20241219 +|Apache-2.0 |org.eclipse.jetty : jetty-http : 9.4.57.v20241219 +|Apache-2.0 |org.eclipse.jetty : jetty-io : 9.4.57.v20241219 +|Apache-2.0 |org.eclipse.jetty : jetty-security : 9.4.57.v20241219 +|Apache-2.0 |org.eclipse.jetty : jetty-server : 9.4.57.v20241219 +|Apache-2.0 |org.eclipse.jetty : jetty-servlet : 9.4.57.v20241219 +|Apache-2.0 |org.eclipse.jetty : jetty-util : 9.4.57.v20241219 +|Apache-2.0 |org.eclipse.jetty : jetty-util-ajax : 9.4.57.v20241219 +|Apache-2.0 |org.ehcache : ehcache : 3.9.3 +|Apache-2.0 |org.fusesource.jansi : jansi : 1.18 +|Apache-2.0 |org.glassfish.jersey.containers : jersey-container-servlet : 2.39.1 +|Apache-2.0 |org.glassfish.jersey.containers : jersey-container-servlet-core : 2.39.1 +|Apache-2.0 |org.glassfish.jersey.core : jersey-client : 2.39.1 +|Apache-2.0 |org.glassfish.jersey.core : jersey-common : 2.39.1 +|Apache-2.0 |org.glassfish.jersey.core : jersey-server : 2.39.1 +|Apache-2.0 |org.glassfish.jersey.ext : jersey-entity-filtering : 2.39.1 +|Apache-2.0 |org.glassfish.jersey.inject : jersey-hk2 : 2.39.1 +|Apache-2.0 |org.glassfish.jersey.media : jersey-media-json-jackson : 2.39.1 +|Apache-2.0 |org.glassfish.jersey.media : jersey-media-multipart : 2.39.1 +|Apache-2.0 |org.jasypt : jasypt : 1.9.2 +|Apache-2.0 |org.jasypt : jasypt : 1.9.3 +|Apache-2.0 |org.javassist : javassist : 3.28.0-ga +|Apache-2.0 |org.jetbrains : annotations : 13.0 +|Apache-2.0 |org.jetbrains : annotations : 26.0.1 +|Apache-2.0 |org.jetbrains.kotlin : kotlin-stdlib : 1.6.20 +|Apache-2.0 |org.jetbrains.kotlin : kotlin-stdlib : 2.1.0 +|Apache-2.0 |org.jetbrains.kotlin : kotlin-stdlib : 2.2.0 +|Apache-2.0 |org.jetbrains.kotlin : kotlin-stdlib-common : 1.6.20 +|Apache-2.0 |org.jetbrains.kotlin : kotlin-stdlib-jdk7 : 1.6.20 +|Apache-2.0 |org.jetbrains.kotlin : kotlin-stdlib-jdk7 : 2.2.0 +|Apache-2.0 |org.jetbrains.kotlin : kotlin-stdlib-jdk8 : 1.6.20 +|Apache-2.0 |org.jetbrains.kotlin : kotlin-stdlib-jdk8 : 2.2.0 +|Apache-2.0 |org.jheaps : jheaps : 0.14 +|Apache-2.0 |org.jline : jline : 3.19.0 +|Apache-2.0 |org.jspecify : jspecify : 1.0.0 +|Apache-2.0 |org.mapdb : mapdb : 1.0.6 +|Apache-2.0 |org.mock-server mockserver-netty 5.13.1 +|Apache-2.0 |org.objenesis : objenesis : 3.3 +|Apache-2.0 |org.objenesis : objenesis : 3.4 +|Apache-2.0 |org.opensaml : opensaml-core : 3.4.6 +|Apache-2.0 |org.opensaml : opensaml-profile-api : 3.4.6 +|Apache-2.0 |org.opensaml : opensaml-saml-api : 3.4.6 +|Apache-2.0 |org.opensaml : opensaml-saml-impl : 3.4.6 +|Apache-2.0 |org.opensaml : opensaml-security-api : 3.4.6 +|Apache-2.0 |org.opensaml : opensaml-security-impl : 3.4.6 +|Apache-2.0 |org.opensaml : opensaml-soap-api : 3.4.6 +|Apache-2.0 |org.opensaml : opensaml-xacml-api : 3.4.6 +|Apache-2.0 |org.opensaml : opensaml-xacml-impl : 3.4.6 +|Apache-2.0 |org.opensaml : opensaml-xacml-saml-api : 3.4.6 +|Apache-2.0 |org.opensaml : opensaml-xacml-saml-impl : 3.4.6 +|Apache-2.0 |org.opensaml : opensaml-xmlsec-api : 3.4.6 +|Apache-2.0 |org.opensaml : opensaml-xmlsec-impl : 3.4.6 +|Apache-2.0 |org.opentest4j : opentest4j : 1.3.0 +|Apache-2.0 |org.parboiled : parboiled_2.12 : 2.5.1 +|Apache-2.0 |org.quartz-scheduler : quartz : 2.5.0 +|Apache-2.0 |org.raml : raml-parser-2 : 1.0.41 +|Apache-2.0 |org.raml : yagi : 1.0.47 +|Apache-2.0 |org.reflections : reflections : 0.10.2 +|Apache-2.0 |org.scala-lang : scala-library : 2.12.18 +|Apache-2.0 |org.scala-lang.modules : scala-parser-combinators_2.12 : 2.1.1 +|Apache-2.0 |org.slf4j : jcl-over-slf4j : 2.0.17 +|Apache-2.0 |org.slf4j : jcl-over-slf4j : 2.0.7 +|Apache-2.0 |org.springframework : spring-aop : 6.2.0 +|Apache-2.0 |org.springframework : spring-aop : 6.2.10 +|Apache-2.0 |org.springframework : spring-beans : 6.2.0 +|Apache-2.0 |org.springframework : spring-beans : 6.2.10 +|Apache-2.0 |org.springframework : spring-context : 6.2.0 +|Apache-2.0 |org.springframework : spring-context : 6.2.10 +|Apache-2.0 |org.springframework : spring-core : 6.2.0 +|Apache-2.0 |org.springframework : spring-core : 6.2.10 +|Apache-2.0 |org.springframework : spring-expression : 6.2.0 +|Apache-2.0 |org.springframework : spring-expression : 6.2.10 +|Apache-2.0 |org.togglz : togglz-core : 4.4.0 +|Apache-2.0 |org.vibur : vibur-object-pool : 26.0 +|Apache-2.0 |org.xmlresolver : xmlresolver : 5.2.2 +|Apache-2.0 |org.xmlresolver : xmlresolver : jar : data : 5.2.2 +|Apache-2.0 |org.yaml : snakeyaml : 2.0 +|Apache-2.0 |org.yaml : snakeyaml : 2.4 +|Bouncycastle-license |org.bouncycastle : bcpkix-jdk15to18 : 1.78 +|Bouncycastle-license |org.bouncycastle : bcprov-jdk15to18 : 1.78 +|Bouncycastle-license |org.bouncycastle : bcutil-jdk15to18 : 1.78 +|BSD |net.java.dev.stax-utils : stax-utils : 20080702 +|BSD-3-Clause |com.esotericsoftware : kryo : 5.5.0 +|BSD-3-Clause |com.esotericsoftware : minlog : 1.3.1 +|BSD-3-Clause |com.esotericsoftware : reflectasm : 1.11.9 +|BSD-3-Clause |com.github.snksoft : crc : 1.1.0 +|BSD-3-Clause |com.google.protobuf : protobuf-java : 3.25.5 +|BSD-3-Clause |com.google.re2j : re2j : 1.6 +|BSD-3-Clause |com.google.re2j : re2j : 1.8 +|BSD-3-Clause |org.antlr : antlr-runtime : 3.5.3 +|BSD-3-Clause |org.dom4j : dom4j : 2.2.0 +|BSD-3-Clause |org.ow2.asm : asm : 9.7.1 +|CC0-1.0 |org.reactivestreams : reactive-streams : 1.0.3 +|CDDL |javax.servlet : javax.servlet-api : 3.1.0 +|CDDL |org.glassfish.grizzly : grizzly-framework : 2.3.34 +|CDDL |org.glassfish.grizzly : grizzly-http : 2.3.34 +|CDDL |org.glassfish.grizzly : grizzly-http-server : 2.3.34 +|CDDL |org.glassfish.grizzly : grizzly-http-servlet : 2.3.34 +|CDDL |org.glassfish.grizzly : grizzly-websockets : 2.3.34 +|CDDL |org.glassfish.grizzly : grizzly-websockets : 2.4.0-beta4 +|CDDL-1.1 |javax.ws.rs : javax.ws.rs-api : 2.0 +|Development License |tanukisoft : wrapper : 3.5.51 +|DOM4j-License |org.dom4j : dom4j : 2.1.4 +|EDL-1.0 |com.sun.activation : jakarta.activation : 1.2.2 +|EDL-1.0 |com.sun.activation : jakarta.activation : 2.0.1 +|EDL-1.0 |com.sun.istack : istack-commons-runtime : 3.0.12 +|EDL-1.0 |com.sun.mail : jakarta.mail : 1.6.3 +|EDL-1.0 |com.sun.mail : jakarta.mail : 2.0.1 +|EDL-1.0 |com.sun.mail : jakarta.mail : 2.0.2 +|EDL-1.0 |com.sun.xml.bind : jaxb-core : 3.0.2 +|EDL-1.0 |com.sun.xml.bind : jaxb-impl : 3.0.2 +|EDL-1.0 |com.sun.xml.messaging.saaj : saaj-impl : 1.5.3 +|EDL-1.0 |jakarta.activation : jakarta.activation-api : 2.1.3 +|EDL-1.0 |jakarta.jws : jakarta.jws-api : 1.1.1 +|EDL-1.0 |jakarta.mail : jakarta.mail-api : 2.1.3 +|EDL-1.0 |jakarta.xml.bind : jakarta.xml.bind-api : 2.3.3 +|EDL-1.0 |jakarta.xml.bind : jakarta.xml.bind-api : 3.0.1 +|EDL-1.0 |jakarta.xml.soap : jakarta.xml.soap-api : 1.4.2 +|EDL-1.0 |jakarta.xml.ws : jakarta.xml.ws-api : 2.3.3 +|EDL-1.0 |org.glassfish.jaxb : jaxb-runtime : 2.3.5 +|EDL-1.0 |org.glassfish.jaxb : txw2 : 2.3.5 +|EDL-1.0 |org.jvnet.mimepull : mimepull : 1.9.15 +|EDL-1.0 |org.jvnet.staxex : stax-ex : 1.8.3 +|EPL-1.0 |com.mchange : c3p0 : 0.11.2 +|EPL-1.0 |com.mchange : mchange-commons-java : 0.3.2 +|EPL-1.0 |org.eclipse.sisu : org.eclipse.sisu.inject : 0.3.5 +|EPL-2.0 |jakarta.annotation : jakarta.annotation-api : 1.3.5 +|EPL-2.0 |jakarta.annotation : jakarta.annotation-api : 2.1.1 +|EPL-2.0 |jakarta.el : jakarta.el-api : 4.0.0 +|EPL-2.0 |jakarta.interceptor : jakarta.interceptor-api : 2.2.0 +|EPL-2.0 |jakarta.jms : jakarta.jms-api : 2.0.3 +|EPL-2.0 |jakarta.jms : jakarta.jms-api : 3.1.0 +|EPL-2.0 |jakarta.json : jakarta.json-api : 2.1.3 +|EPL-2.0 |jakarta.servlet : jakarta.servlet-api : 4.0.4 +|EPL-2.0 |jakarta.transaction : jakarta.transaction-api : 1.3.3 +|EPL-2.0 |jakarta.transaction : jakarta.transaction-api : 2.0.1 +|EPL-2.0 |jakarta.ws.rs : jakarta.ws.rs-api : 2.1.6 +|EPL-2.0 |org.eclipse.parsson : parsson : 1.1.7 +|EPL-2.0 |org.eclipse.sisu : org.eclipse.sisu.inject : 0.9.0.m3 +|EPL-2.0 |org.eclipse.sisu : org.eclipse.sisu.plexus : 0.9.0.m3 +|EPL-2.0 |org.glassfish.hk2 : hk2-api : 2.6.1 +|EPL-2.0 |org.glassfish.hk2 : hk2-locator : 2.6.1 +|EPL-2.0 |org.glassfish.hk2 : hk2-utils : 2.6.1 +|EPL-2.0 |org.glassfish.hk2 : osgi-resource-locator : 1.0.3 +|EPL-2.0 |org.glassfish.hk2.external : aopalliance-repackaged : 2.6.1 +|EPL-2.0 |org.glassfish.hk2.external : jakarta.inject : 2.6.1 +|EPL-2.0 |org.jacoco : org.jacoco.agent : jar : runtime : 0.8.8 +|EPL-2.0 |org.jgrapht : jgrapht-core : 1.5.2 +|EPL-2.0 |org.junit.jupiter : junit-jupiter-api : 5.13.4 +|EPL-2.0 |org.junit.platform : junit-platform-commons : 1.13.4 +|EPL-2.0 |org.junit.platform : junit-platform-engine : 1.13.4 +|EPL-2.0 |org.junit.platform : junit-platform-launcher : 1.13.4 +|JSON |org.json : json : 20210307 +|JSON |org.json : json : 20210307 +|LGPL-2.1 |com.github.spotbugs : spotbugs-annotations : 4.7.3 +|LGPL-2.1 |org.codelibs : jcifs : 1.3.18.3 +|MIT |com.github.oshi : oshi-core : 6.6.4 +|MIT |com.vdurmont : semver4j : 3.1.0 +|MIT |handlebars 4.7.7 +|MIT |me.tongfei : progressbar : 0.9.1 +|MIT |net.sf.jopt-simple : jopt-simple : 5.0.3 +|MIT |org.apfloat : apfloat : 1.14.0 +|MIT |org.apfloat : apfloat : 1.14.0 +|MIT |org.checkerframework : checker-qual : 3.19.0 +|MIT |org.checkerframework : checker-qual : 3.33.0 +|MIT |org.checkerframework : checker-qual : 3.48.3 +|MIT |org.checkerframework : checker-qual : 3.49.5 +|MIT |org.jsoup : jsoup : 1.21.1 +|MIT |org.slf4j : jul-to-slf4j : 2.0.17 +|MIT |org.slf4j : jul-to-slf4j : 2.0.7 +|MIT |org.slf4j : slf4j-api : 1.7.30 +|MIT |org.slf4j : slf4j-api : 2.0.17 +|MIT |org.webjars hal-explorer 0.12.0 +|MIT |superstartup-closure-compiler 0.1.1 +|MIT-0 |org.reactivestreams : reactive-streams : 1.0.4 +|MPL-1.1 |com.googlecode.juniversalchardet : juniversalchardet : 1.0.3 +|MPL-2.0 |org.mozilla : rhino : 1.8.0 +|MPL-2.0 |org.mozilla : rhino-engine : 1.8.0 +|Public Domain |aopalliance : aopalliance : 1.0 +|Public Domain |org.json : json : 20231013 +|Public Domain |org.json : json : 20250517 |=== == License Information From 62fac3b9c32978c5d470783bcd27240aaa1b8cf6 Mon Sep 17 00:00:00 2001 From: Daniela Merlo <97902112+dmerlob@users.noreply.github.com> Date: Thu, 11 Sep 2025 17:33:40 -0300 Subject: [PATCH 14/33] Update modules/ROOT/pages/third-party-software-in-mule.adoc --- modules/ROOT/pages/third-party-software-in-mule.adoc | 1 - 1 file changed, 1 deletion(-) diff --git a/modules/ROOT/pages/third-party-software-in-mule.adoc b/modules/ROOT/pages/third-party-software-in-mule.adoc index 9cd159851..6aa91f4ac 100644 --- a/modules/ROOT/pages/third-party-software-in-mule.adoc +++ b/modules/ROOT/pages/third-party-software-in-mule.adoc @@ -50,7 +50,6 @@ The following table lists third-party software in Mule sorted by software compon |Apache-2.0 |com.github.java-json-tools : json-schema-core : 1.2.10 |Apache-2.0 |com.github.java-json-tools : json-schema-validator : 2.2.10 |Apache-2.0 |com.github.jknack : handlebars : 4.3.1 -|Apache-2.0 |com.github.jknack : handlebars : 4.3.1 |Apache-2.0 |com.github.jknack : handlebars-proto : 4.1.0 |Apache-2.0 |com.github.jsendnsca : jsendnsca : 2.1.1 |Apache-2.0 |com.github.pjfanning : excel-streaming-reader : 4.1.2 From cf30836055695fecdfee0ca8063d6122e2a32e77 Mon Sep 17 00:00:00 2001 From: Daniela Merlo <97902112+dmerlob@users.noreply.github.com> Date: Thu, 11 Sep 2025 17:33:51 -0300 Subject: [PATCH 15/33] Update modules/ROOT/pages/third-party-software-in-mule.adoc --- modules/ROOT/pages/third-party-software-in-mule.adoc | 1 - 1 file changed, 1 deletion(-) diff --git a/modules/ROOT/pages/third-party-software-in-mule.adoc b/modules/ROOT/pages/third-party-software-in-mule.adoc index 6aa91f4ac..5715b69cf 100644 --- a/modules/ROOT/pages/third-party-software-in-mule.adoc +++ b/modules/ROOT/pages/third-party-software-in-mule.adoc @@ -21,7 +21,6 @@ The following table lists third-party software in Mule sorted by software compon |Apache-2.0 |com.conversantmedia : disruptor : 1.2.21 |Apache-2.0 |com.damnhandy : handy-uri-templates : 2.1.8 |Apache-2.0 |com.esotericsoftware : kryo-shaded : 4.0.3 -|Apache-2.0 |com.esotericsoftware : kryo-shaded : 4.0.3 |Apache-2.0 |com.fasterxml : aalto-xml : 1.3.2 |Apache-2.0 |com.fasterxml.jackson.core : jackson-annotations : 2.16.0 |Apache-2.0 |com.fasterxml.jackson.core : jackson-annotations : 2.17.2 From fcd3f007abe59033314fefd3a9e8d3fe172b88c3 Mon Sep 17 00:00:00 2001 From: Daniela Merlo Date: Fri, 12 Sep 2025 19:06:12 -0300 Subject: [PATCH 16/33] W-19450029-featureFlag-410-dm --- modules/ROOT/pages/feature-flagging.adoc | 35 +++++++++++++++++++++++- 1 file changed, 34 insertions(+), 1 deletion(-) diff --git a/modules/ROOT/pages/feature-flagging.adoc b/modules/ROOT/pages/feature-flagging.adoc index 307c228e7..03fa48ad5 100644 --- a/modules/ROOT/pages/feature-flagging.adoc +++ b/modules/ROOT/pages/feature-flagging.adoc @@ -778,11 +778,44 @@ This feature isn't configurable by system property. *Enabled by Default Since* -* Not enabled by default in any Mule version +* 4.10.0 *Issue ID* * W-16941297 +<.^|`USE_SEPARATE_CLASSLOADER_FOR_POLICY_ISOLATION_PROPERTY` +|When enabled, policy isolation uses a dedicated classloader environment, separate from the domain's, to avoid dependency conflicts. This setup ensures that policies run with their own set of dependencies. + +*Available Since* + +* 4.10.0 +* 4.9.5 +* 4.6.17 + +*Enabled by Default Since* + +* 4.10.0 + +*Issue ID* + +* W-17340911 +<.^|`REPEATABLE_STREAMING_BYTES_EAGER_READ_PROPERTY` +|When enabled, the `read` methods of bytes repeatable streams return immediately with any available data. If disabled, they don't return until the requested `len` is fully read. Set this property to true to process SSE events over HTTP as they arrive instead of buffering them. + +*Available Since* + +* 4.10.0 +* 4.9.7 +* 4.6.20 +* 4.4.1 + +*Enabled by Default Since* + +* 4.10.0 + +*Issue ID* + +* W-18716253 |=== == See Also From 2b0557c3256ad5b2340e8ac130ca5512f9f18126 Mon Sep 17 00:00:00 2001 From: Daniela Merlo Date: Tue, 16 Sep 2025 16:41:58 -0300 Subject: [PATCH 17/33] W-19652742-MMP-runtimeVersion-dm --- .../pages/package-a-mule-application.adoc | 26 ++++++++++++++++--- 1 file changed, 23 insertions(+), 3 deletions(-) diff --git a/modules/ROOT/pages/package-a-mule-application.adoc b/modules/ROOT/pages/package-a-mule-application.adoc index 13f7cbe9e..53235d2f5 100644 --- a/modules/ROOT/pages/package-a-mule-application.adoc +++ b/modules/ROOT/pages/package-a-mule-application.adoc @@ -16,7 +16,7 @@ This file describes all the dependencies required by the package to work properl == Compatibility -Mule 4 applications are compatible with the following Anypoint Studio and Mule Maven Plugin versions: +Mule 4 applications are compatible with these Anypoint Studio and Mule Maven Plugin versions: * Anypoint Studio 7.x * Mule Maven Plugin 3.x @@ -27,6 +27,26 @@ Mule 4 applications are compatible with the following Anypoint Studio and Mule M + See xref:mmp-concept.adoc#add-mmp[Add the Mule Maven Plugin to a Mule Project] for instructions. +== Specify the Mule Runtime Version for Packaging + +You can specify the Mule runtime version that the Mule framework uses during the packaging process by adding the `runtimeVersion` property in the Mule Maven plugin configuration in your `pom.xml` file: + +[source,xml,linenums] +---- + + org.mule.tools.maven + mule-maven-plugin + ${mule.maven.plugin.version} + true + + 4.9.6 + + +---- + +[NOTE] +By default, Mule Maven plugin selects a Mule runtime version that is compatible with the plugin's framework version. If you set a specific `runtimeVersion` to use a particular Mule runtime patch, you can encounter compatibility issues if that patch isn't supported by the framework version in use. + == Mule Application Structure Reference At design time, your Mule application must have at least these three basic components: @@ -163,7 +183,7 @@ When you package an application, you can exclude certain files or directories. C Each line in a `_muleExclude` file specifies a rule that follows the https://docs.oracle.com/javase/tutorial/essential/io/fileOps.html#glob[glob pattern]. -For example, consider the following `_muleExclude` file which contains two exclusion rules: +For example, consider this `_muleExclude` file that contains two exclusion rules: ---- fileToBeExcluded.json **/src/main/resources/local_directory @@ -176,4 +196,4 @@ If `**/src/main/resources/local_directory` is replaced with `local_directory` th == See Also * xref:studio::import-export-packages.adoc#export-project-studio[Exporting Projects from Studio] -* xref:mmp-concept.adoc[Mule Maven Plugin] +* xref:mmp-concept.adoc[Mule Maven Plugin] \ No newline at end of file From f80094cecec384f8638615af3649aca3e8b49c26 Mon Sep 17 00:00:00 2001 From: Daniela Merlo <97902112+dmerlob@users.noreply.github.com> Date: Wed, 17 Sep 2025 12:02:32 -0300 Subject: [PATCH 18/33] Update modules/ROOT/pages/package-a-mule-application.adoc --- modules/ROOT/pages/package-a-mule-application.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/ROOT/pages/package-a-mule-application.adoc b/modules/ROOT/pages/package-a-mule-application.adoc index 53235d2f5..3c3443491 100644 --- a/modules/ROOT/pages/package-a-mule-application.adoc +++ b/modules/ROOT/pages/package-a-mule-application.adoc @@ -29,7 +29,7 @@ See xref:mmp-concept.adoc#add-mmp[Add the Mule Maven Plugin to a Mule Project] f == Specify the Mule Runtime Version for Packaging -You can specify the Mule runtime version that the Mule framework uses during the packaging process by adding the `runtimeVersion` property in the Mule Maven plugin configuration in your `pom.xml` file: +Starting with Mule Maven plugin 4.6.0, tou can specify the Mule runtime version that the Mule framework uses during the packaging process by adding the `runtimeVersion` property in the Mule Maven plugin configuration in your `pom.xml` file: [source,xml,linenums] ---- From fc7478e0d8d0144aaa8de58726afcb983832a924 Mon Sep 17 00:00:00 2001 From: Daniela Merlo <97902112+dmerlob@users.noreply.github.com> Date: Wed, 17 Sep 2025 12:04:31 -0300 Subject: [PATCH 19/33] Update modules/ROOT/pages/package-a-mule-application.adoc --- modules/ROOT/pages/package-a-mule-application.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/ROOT/pages/package-a-mule-application.adoc b/modules/ROOT/pages/package-a-mule-application.adoc index 3c3443491..f37e19dd2 100644 --- a/modules/ROOT/pages/package-a-mule-application.adoc +++ b/modules/ROOT/pages/package-a-mule-application.adoc @@ -29,7 +29,7 @@ See xref:mmp-concept.adoc#add-mmp[Add the Mule Maven Plugin to a Mule Project] f == Specify the Mule Runtime Version for Packaging -Starting with Mule Maven plugin 4.6.0, tou can specify the Mule runtime version that the Mule framework uses during the packaging process by adding the `runtimeVersion` property in the Mule Maven plugin configuration in your `pom.xml` file: +Starting with Mule Maven plugin 4.6.0, you can specify the Mule runtime version that the Mule framework uses during the packaging process by adding the `runtimeVersion` property in the Mule Maven plugin configuration in your `pom.xml` file: [source,xml,linenums] ---- From d26437ae7ea6838507d8e113a818c92a8f9896e8 Mon Sep 17 00:00:00 2001 From: Daniela Merlo Date: Wed, 17 Sep 2025 14:03:53 -0300 Subject: [PATCH 20/33] W-19420663-troubleshootingPLUGIN-update-dm --- .../pages/mule-troubleshooting-plugin.adoc | 78 ++++++++++--------- 1 file changed, 41 insertions(+), 37 deletions(-) diff --git a/modules/ROOT/pages/mule-troubleshooting-plugin.adoc b/modules/ROOT/pages/mule-troubleshooting-plugin.adoc index fc49e2ba8..a8011246f 100644 --- a/modules/ROOT/pages/mule-troubleshooting-plugin.adoc +++ b/modules/ROOT/pages/mule-troubleshooting-plugin.adoc @@ -11,18 +11,21 @@ This Java-based plugin provides an extensible, environment-agnostic solution tha == Before You Begin -Before using the plugin, make sure that you have the following prerequisites: +Before using the plugin, make sure that you have these prerequisites: * Mule runtime distribution starting with 4.10, with patches available for 4.6 and 4.9. * Java 8 or later, matching the Mule runtime version requirements. * Access to `$MULE_HOME`. The CLI script `diag` automatically locates the Mule home directory. -The plugin works out-of-the-box in all deployment models (Standalone, CloudHub, CloudHub 2.0, Runtime Fabric) without installing additional dependencies. +The plugin works out-of-the-box in all deployment models (Standalone, CloudHub, CloudHub 2.0, Anypoint Runtime Fabric) without installing additional dependencies. == Using the Mule Troubleshooting Plugin -Run the following command from your Mule runtime installation at `$MULE_HOME/tools/diag` to generate the DIAF and a thread dump. By default, this creates a ZIP file named `mule_dump_[timestamp].zip`. -Use the `./diag --support` command to generate a heap dump. The Mule dump is saved in the `logs` directory by default, or use the `./diag --output` command to save the dump to a different path. +Run this command from your Mule runtime installation at `$MULE_HOME/tools/diag` to generate the DIAF and a thread dump. By default, the tool saves the files unzipped in the `logs` directory of the distribution. + +Use the `./diag --extended` command to generate a heap dump. Use `./diag --output some/dir/name/` to create the directories if they don't exist and save unzipped files there. Use `./diag --output some/dir/name` (without a trailing `/`) to create a ZIP file at that path containing all output files. + +On Windows, run `diag.bat`. The `--stdout` option isn't supported. The plugin's help output lists the available commands and options. @@ -42,13 +45,13 @@ Commands: Global Options: --stdout Output the diagnostic dump to standard output --output Specify custom output directory or file path - --support Enable support mode (includes heap dump) + --extended Enable extended mode (includes heap dump) --debug Enable debug mode with remote debugging on port 5005 Examples: ./diag # Generate diagnostic dump to logs directory ./diag --stdout # Output diagnostic dump to stdout - ./diag --support # Include heap dump in diagnostic + ./diag --extended # Include heap dump in diagnostic ./diag --output /tmp/mule.zip # Save to specific file ./diag --output /tmp/ # Save to specific directory ./diag # Execute specific operation @@ -57,14 +60,14 @@ Output: By default, the tool creates a ZIP file containing: - mule_dump_.diaf # Diagnostic information - thread_dump_.txt # Thread dump - - heap_dump_.hprof # Heap dump (if --support is used) + - heap_dump_.hprof # Heap dump (if --extended is used) The ZIP file is saved to the 'logs' directory by default. ---- == Understanding Diagnostic Information Analysis File (DIAF) -The Diagnostic Information Analysis File (DIAF) groups all diagnostic data collected by the Mule Troubleshooting plugin into structured sections. Use this reference to understand the content of each section: +The Diagnostic Information Analysis File (DIAF) organizes all diagnostic data collected by the Mule Troubleshooting plugin into structured sections. Use this reference to understand the content of each section: * <> * <> @@ -102,7 +105,7 @@ This section shows details about the environment where the Mule runtime instance | Absolute path to `MULE_HOME` for the Mule runtime. | `mule_base` -| Absolute path to MULE_BASE for the Mule runtime. +| Absolute path to `MULE_BASE` for the Mule runtime. | `mule.*` System Properties | All system properties starting with `mule.`, including those defined by DataWeave and API Gateway. Listed with values and sorted alphabetically. @@ -173,6 +176,31 @@ This section shows details about the environment where the Mule runtime instance This section shows detailed statistics information about deployed Mule applications and their performance metrics. +==== Flow Summary Statistics + +[cols="1,3", options="header"] +|=== +| Field | Description + +| Private Flows Declared +| Total number of private flows declared in the application. A private flow doesn't contain a `MessageSource` and isn't used by an APIkit router. + +| Private Flows Active +| Number of private flows that are currently in a started state. + +| Trigger Flows Declared +| Total number of trigger flows declared in the application. A trigger flow contains a MessageSource. + +| Trigger Flows Active +| Number of trigger flows currently in a started state. + +| API Kit Flows Declared +| Total number of APIkit flows declared in the application. An APIkit flow is used by an APIkit router but doesn't contain a `MessageSource`. + +| API Kit Flows Active +| Number of APIkit flows currently in a started state. +|=== + ==== General Application Metrics [cols="1,3", options="header"] @@ -210,31 +238,6 @@ This section shows detailed statistics information about deployed Mule applicati | Cumulative time (in milliseconds) spent processing all events. |=== -==== Flow Summary Statistics - -[cols="1,3", options="header"] -|=== -| Field | Description - -| Private Flows Declared -| Total number of private flows declared in the application. A private flow doesn't contain a `MessageSource` and isn't used by an APIkit router. - -| Private Flows Active -| Number of private flows that are currently in a started state. - -| Trigger Flows Declared -| Total number of trigger flows declared in the application. A trigger flow contains a MessageSource. - -| Trigger Flows Active -| Number of trigger flows currently in a started state. - -| API Kit Flows Declared -| Total number of APIkit flows declared in the application. An APIkit flow is used by an APIkit router but doesn't contain a `MessageSource`. - -| API Kit Flows Active -| Number of APIkit flows currently in a started state. -|=== - ==== Flow Statistics [cols="1,3", options="header"] @@ -266,7 +269,7 @@ This section shows detailed statistics information about deployed Mule applicati [[diaf-fuse-board]] === Fuse Board -This section shows alerts for known Mule runtime issues. The report lists how many times each alert triggers during the last 1, 5, 15, and 60 minutes along with the context of the alert at the time of triggering. Some alerts trigger multiple times with the same context, such as the backpressure alert, so the plugin shows the context once and indicates how many times it happens to avoid flooding the report. Alerts that don't trigger in any of the time intervals aren't included in the report. +This section shows alerts for known Mule runtime issues. The report lists how many times each alert triggers during the last 1, 5, 15, and 60 minutes along with the context of the alert at the time of triggering. Some alerts, like the backpressure alert, trigger multiple times with the same context, so the plugin shows the context once and indicates how many times it happens to avoid flooding the report. Alerts that don't trigger in any of the time intervals aren't included in the report. [cols="1,3", options="header"] |=== @@ -389,11 +392,12 @@ a| Type of tasks the scheduler runs: == Technical Considerations * DIAF provides investigation hints. Check the logs for complete details. -* Heap dumps may contain sensitive data. Enable `--support` only in secure environments. +* Heap dumps may contain sensitive data. Enable `--extended` only in secure environments. * In Mule runtime instances with multiple applications, DIAF sections are grouped by application. == Best Practices * Use DIAF for initial troubleshooting before collecting heap or thread dumps manually. * Correlate events in the event dump section with logs by using the `eventId` for deeper analysis. -* Collect scheduled diagnostics during maintenance windows in production environments. \ No newline at end of file +* Collect scheduled diagnostics during maintenance windows in production environments. +* For TLS deprecation, enable `mule.extractConnectionData.enable` to generate `.mule/.introspection/connections_data_.csv`. On UNIX, the tool generates `_tls_results.csv` along with DIAF output. Enable `mule.extractConnectionData.silentErrors` to log errors without failing deployment. \ No newline at end of file From 6f0f03c4b1b5217f777f3fe87f380a54d2c0191a Mon Sep 17 00:00:00 2001 From: Daniela Merlo <97902112+dmerlob@users.noreply.github.com> Date: Wed, 17 Sep 2025 16:09:16 -0300 Subject: [PATCH 21/33] Update modules/ROOT/pages/mule-troubleshooting-plugin.adoc --- modules/ROOT/pages/mule-troubleshooting-plugin.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/ROOT/pages/mule-troubleshooting-plugin.adoc b/modules/ROOT/pages/mule-troubleshooting-plugin.adoc index a8011246f..acb908e15 100644 --- a/modules/ROOT/pages/mule-troubleshooting-plugin.adoc +++ b/modules/ROOT/pages/mule-troubleshooting-plugin.adoc @@ -17,7 +17,7 @@ Before using the plugin, make sure that you have these prerequisites: * Java 8 or later, matching the Mule runtime version requirements. * Access to `$MULE_HOME`. The CLI script `diag` automatically locates the Mule home directory. -The plugin works out-of-the-box in all deployment models (Standalone, CloudHub, CloudHub 2.0, Anypoint Runtime Fabric) without installing additional dependencies. +The plugin works out-of-the-box in the Standalone and CloudHub deployment models without installing additional dependencies. == Using the Mule Troubleshooting Plugin From 9b9b96cc3fde41d9da3ef07458b5bc35ff3dfd36 Mon Sep 17 00:00:00 2001 From: Daniela Merlo Date: Thu, 18 Sep 2025 13:28:31 -0300 Subject: [PATCH 22/33] W-19420663-more info added --- .../pages/mule-troubleshooting-plugin.adoc | 62 ++++++++++--------- 1 file changed, 32 insertions(+), 30 deletions(-) diff --git a/modules/ROOT/pages/mule-troubleshooting-plugin.adoc b/modules/ROOT/pages/mule-troubleshooting-plugin.adoc index acb908e15..5331e30cb 100644 --- a/modules/ROOT/pages/mule-troubleshooting-plugin.adoc +++ b/modules/ROOT/pages/mule-troubleshooting-plugin.adoc @@ -3,9 +3,9 @@ ifndef::env-site,env-github[] include:: endif::[] -Use the Mule Troubleshooting plugin to generate structured diagnostic information, simplify troubleshooting, and provide consistent data for Mule runtime support. +Use the Mule Troubleshooting plugin to generate structured diagnostic information, simplify troubleshooting, and provide consistent data for Mule runtime support. -The Mule Troubleshooting plugin provides a unified way to collect diagnostic data from Mule runtime environments. It generates a structured diagnostic archive called the Diagnostic Information Analysis File (DIAF), which consolidates Mule runtime information, application metrics, and system data into a single, standardized output. +The Mule Troubleshooting plugin provides a unified way to collect diagnostic data from Mule runtime environments. It generates a structured diagnostic archive called the Diagnostic Information Analysis File (DIAF), which consolidates Mule runtime information, application metrics, and system data into a single, standardized output. This Java-based plugin provides an extensible, environment-agnostic solution that simplifies troubleshooting for Mule runtime engineers, MuleSoft Support teams, customers running self-service diagnostics, and AI-assisted analysis. @@ -21,7 +21,7 @@ The plugin works out-of-the-box in the Standalone and CloudHub deployment models == Using the Mule Troubleshooting Plugin -Run this command from your Mule runtime installation at `$MULE_HOME/tools/diag` to generate the DIAF and a thread dump. By default, the tool saves the files unzipped in the `logs` directory of the distribution. +Run this command from your Mule runtime installation at `$MULE_HOME/tools/diag` to generate the DIAF and a thread dump. By default, the tool saves the files unzipped in the `logs` directory of the distribution. Use the `./diag --extended` command to generate a heap dump. Use `./diag --output some/dir/name/` to create the directories if they don't exist and save unzipped files there. Use `./diag --output some/dir/name` (without a trailing `/`) to create a ZIP file at that path containing all output files. @@ -72,7 +72,7 @@ The Diagnostic Information Analysis File (DIAF) organizes all diagnostic data co * <> * <> * <> -* <> +* <> * <> * <> @@ -147,7 +147,7 @@ This section shows details about the environment where the Mule runtime instance | Amount of used memory in the JVM. | `memory.free` -| Amount of free memory in the JVM. +| Amount of available memory in the JVM. | `memory.total` | Total amount of memory in the JVM. @@ -174,7 +174,9 @@ This section shows details about the environment where the Mule runtime instance [[diaf-statistics]] === Statistics -This section shows detailed statistics information about deployed Mule applications and their performance metrics. +This section shows detailed statistics information about deployed Mule applications and their performance metrics. Metrics reflect the runtime state since the last start or redeployment. They reset after redeployments and don't capture complete historical data. Don't use these metrics for pricing or commercial purposes, as they provide a snapshot of runtime behavior. + +Set the property `mule.enable.statistics` to collect General Application Metrics and Flow Statistics. ==== Flow Summary Statistics @@ -195,7 +197,7 @@ This section shows detailed statistics information about deployed Mule applicati | Number of trigger flows currently in a started state. | API Kit Flows Declared -| Total number of APIkit flows declared in the application. An APIkit flow is used by an APIkit router but doesn't contain a `MessageSource`. +| Total number of APIkit flows declared in the application. An APIkit router uses an APIkit flow, but the flow doesn't contain a `MessageSource`. | API Kit Flows Active | Number of APIkit flows currently in a started state. @@ -266,8 +268,8 @@ This section shows detailed statistics information about deployed Mule applicati | Average time (in milliseconds) required to process an event. |=== -[[diaf-fuse-board]] -=== Fuse Board +[[diaf-alerts]] +=== Alerts This section shows alerts for known Mule runtime issues. The report lists how many times each alert triggers during the last 1, 5, 15, and 60 minutes along with the context of the alert at the time of triggering. Some alerts, like the backpressure alert, trigger multiple times with the same context, so the plugin shows the context once and indicates how many times it happens to avoid flooding the report. Alerts that don't trigger in any of the time intervals aren't included in the report. @@ -276,25 +278,25 @@ This section shows alerts for known Mule runtime issues. The report lists how ma | Field | Description | `MULE:UNKNOWN` error raised -| `MULE:UNKNOWN` errors are generated by the runtime and go unhandled. If such an error raises or appears in the app log, it indicates a bug in the Mule runtime. The context shows the details of the errors catalogued as `MULE:UNKNOWN`. +| The runtime generated `MULE:UNKNOWN` errors, which go unhandled. If such an error raises or appears in the app log, it indicates an error in the Mule runtime. The context shows the details of the errors categorized as `MULE:UNKNOWN`. -| Reactor discarded event -| A discarded event is one that a component explicitly filters in a flow. This effectively cuts the processing of such event, causing the execution to hang. The context shows the correlation ID of each discarded event. +| Reactor discarded event +| A discarded event is one that a component explicitly filters in a flow. This cuts the processing of such an event, causing the execution to hang. The context shows the correlation ID of each discarded event. | Reactor dropped event -| A dropped event doesn't properly pass to the following component in a flow through a reactor chain and doesn't complete. Its symptom is that the event is “hanged”. No context is shown for this alert because information is already available in the event dump. +| A dropped event doesn't pass to the following component in a flow through a reactor chain and doesn't complete. Its symptom is that the event is “hanged”. The alert doesn't show context because the event dump provides the information. | Reactor dropped error -| A dropped error doesn't properly pass to the corresponding error handler in a flow through a reactor chain, and so doesn't complete. Its symptom is that the event is “hanged” when an error occurs. The context shows the string representation of each dropped error. +| A dropped error doesn't pass to the corresponding error handler in a flow through a reactor chain, and so doesn't complete. Its symptom is that the event is “hanged” when an error occurs. The context shows the string representation of each dropped error. | Not consumed stream -| A stream that is garbage collected before being completely consumed may provoke leaks on certain conditions (the most common one is connections from a DB connection pool that remain taken until the data is fully read). The context shows the originating location of the components that generated the streams. +| A stream that is garbage collected before being completely consumed can provoke leaks on certain conditions (the most common one is connections from a DB connection pool that remain taken until the data is fully read). The context shows the originating location of the components that generated the streams. | Backpressure triggered -| Backpressure is the mechanism by which incoming events in excess of current capacity are rejected. This happens because of a spike of incoming events or a longer than usual processing time of the flows. A common sign is when backpressure triggers on systems that have a CPU and memory capacity. The context shows the flow or component that exceeded capacity and the reason for backpressure. +| Backpressure is the mechanism that rejects incoming events that exceed the current capacity. This happens because of a spike of incoming events or a longer than usual processing time of the flows. A common sign is when backpressure triggers on systems that have a CPU and memory capacity. The context shows the flow or component that exceeded capacity and the reason for backpressure. | XA recovery start error -| Triggered when recovery of an XA connection fails to start. The context shows the unique name (including the config name) of the connection for which recovery fails. +| Triggered if recovery of an XA connection fails to start. The context shows the unique name (including the configuration name) of the connection for which recovery fails. | Async logger ringbuffer full | When a log appender writes logs slower than the log entries are generated, the logger ringbuffer fills up. When full, threads attempting to log either wait for space in the ringbuffer or log synchronously, depending on the configuration. In either case, a thread that shouldn't block or wait does so, causing performance issues in the Mule runtime. No context is available for this alert because it always means the same, the buffer is full. @@ -327,8 +329,8 @@ a| * `COMPLETE`: Same as `RESPONSE_PROCESSED`, and all child events are `RESPONSE_PROCESSED`. * `TERMINATED`: After `COMPLETE`, and all completion callbacks of the context execute. -| `flowStack` -a| `flowStack` is composed by zero-to-many lines, each with this format. +| `flowStack` +a| `flowStack` contains zero-to-many lines, each with this format. [source,xml] ---- at [componentId]@[componentLocation]([muleFileName]:[muleFileLineNumber]) [timeInLocation] ms @@ -338,13 +340,13 @@ at [componentId]@[componentLocation]([muleFileName]:[muleFileLineNumber]) [timeI | Identifier of the component (for example, `http:request`). | `flowStack.componentLocation` -| Unique identifier of a component within a Mule application. The first part is the flow or policy name, followed by the index and chains where the component is nested. +| Unique identifier of a component within a Mule application. The first part is the flow or policy name, followed by the index and chains that nests the component. | `flowStack.muleFileName` -| Name of the Mule config file where the component is located. +| Name of the Mule configuration file that contains the component. | `flowStack.muleFileLineNumber` -| Line number in the Mule configuration file where the component is located. +| Line number in the Mule configuration file that contains the component. | `flowStack.timeInLocation` | Duration in milliseconds the event spends at the `flowStack` entry. @@ -353,7 +355,7 @@ at [componentId]@[componentLocation]([muleFileName]:[muleFileLineNumber]) [timeI [[diaf-schedulers]] === Schedulers -This section shows the status and metrics of each scheduler. For Mule runtime instances with multiple deployed applications, entries are grouped by application. +This section shows the status and metrics of schedulers provided by the xref:scheduler-concept.adoc[scheduler] service, not the source components themselves. For Mule runtime instances with multiple deployed applications, entries are grouped by application. [cols="1,3", options="header"] |=== @@ -368,7 +370,7 @@ a| Type of tasks the scheduler runs: * `IO`: A task that spends most of its execution waiting for I/O operations to complete. * `CPU_INTENSIVE`: A task that runs longer than 10 milliseconds, with less than 20% of time blocked. * `CPU_LIGHT`: A task that never blocks and runs is less than 10 milliseconds. -* `CUSTOM`: Threads that aren't managed by Mule runtime or shared between schedulers. Used when a thread pool needs exclusive use (for example, NIO selectors). +* `CUSTOM`: Threads that aren't managed by Mule runtime or shared among schedulers. Used when a thread pool needs exclusive use (for example, NIO selectors). | `shutdown` | A shutdown scheduler doesn't accept new tasks. Tasks still running are allowed a graceful period to complete. @@ -391,13 +393,13 @@ a| Type of tasks the scheduler runs: == Technical Considerations -* DIAF provides investigation hints. Check the logs for complete details. -* Heap dumps may contain sensitive data. Enable `--extended` only in secure environments. -* In Mule runtime instances with multiple applications, DIAF sections are grouped by application. +* DIAF provides investigation hints. Check the logs for complete details. +* Heap dumps can contain sensitive data. Enable `--extended` only in secure environments. +* In Mule runtime instances with multiple applications, DIAF sections are grouped by application. == Best Practices -* Use DIAF for initial troubleshooting before collecting heap or thread dumps manually. -* Correlate events in the event dump section with logs by using the `eventId` for deeper analysis. +* Use DIAF for initial troubleshooting before collecting heap or thread dumps manually. +* Correlate events in the event dump section with logs by using the `eventId` for deeper analysis. * Collect scheduled diagnostics during maintenance windows in production environments. -* For TLS deprecation, enable `mule.extractConnectionData.enable` to generate `.mule/.introspection/connections_data_.csv`. On UNIX, the tool generates `_tls_results.csv` along with DIAF output. Enable `mule.extractConnectionData.silentErrors` to log errors without failing deployment. \ No newline at end of file +* To verify if all the hosts defined in your deployable artifacts (domains, applications, policies) support TLS 1.2 and 1.3 connectivity, enable `mule.extractConnectionData.enable`. On UNIX, the tool generates `_tls_results.csv` along with DIAF output. Enable `mule.extractConnectionData.silentErrors` to log errors without failing deployment. Not available for Windows. From 85967f786d4fadefb80f8d8d056a4abde14e7ab4 Mon Sep 17 00:00:00 2001 From: Daniela Merlo Date: Fri, 19 Sep 2025 12:03:05 -0300 Subject: [PATCH 23/33] W-19450029-more flags --- modules/ROOT/pages/feature-flagging.adoc | 63 +++++++++++++++++++++++- 1 file changed, 61 insertions(+), 2 deletions(-) diff --git a/modules/ROOT/pages/feature-flagging.adoc b/modules/ROOT/pages/feature-flagging.adoc index 03fa48ad5..e91a4afe8 100644 --- a/modules/ROOT/pages/feature-flagging.adoc +++ b/modules/ROOT/pages/feature-flagging.adoc @@ -386,7 +386,7 @@ Suppressed errors are treated as underlying causes that can also be matched by O *Issue ID* * W-11071481 -<.^|`ENFORCE_ERROR_TYPES_VALIDATION` +<.^|`ENFORCE_ERROR_TYPES_VALIDATION` |When enabled, error types validations are enforced, even for error handlers/components that aren't being referenced. This feature isn't configurable by system property. @@ -799,7 +799,7 @@ This feature isn't configurable by system property. *Issue ID* * W-17340911 -<.^|`REPEATABLE_STREAMING_BYTES_EAGER_READ_PROPERTY` +<.^|`mule.repeatableStreaming.bytes.eagerRead` |When enabled, the `read` methods of bytes repeatable streams return immediately with any available data. If disabled, they don't return until the requested `len` is fully read. Set this property to true to process SSE events over HTTP as they arrive instead of buffering them. *Available Since* @@ -816,6 +816,65 @@ This feature isn't configurable by system property. *Issue ID* * W-18716253 +<.^|`mule.disable.optimised.notification.handler.dynamic.resolution.update.based.on.delegate` +|When disabled, dynamic resolution of notification handling doesn't occur after the Mule artifact initializes. This can result in race conditions that affect monitoring metrics. + +*Available Since* + +* 4.10.0 + +*Enabled by Default Since* + +* Not enabled by default in any Mule version. + +*Issue ID* + +* W- +<.^|`mule.gracefulShutdown.defaultTimeout` +|Sets the default graceful shutdown time for an application in milliseconds. Mule uses this value only if `shutdownTimeout` isn't set in the application configuration. If this default isn't set, the default is 5000 milliseconds. + +*Available Since* + +* 4.10.0 +* 4.9.5 +* 4.6.17 +* 4.4.0-20250530 + +*Enabled by Default Since* + +* Not enabled by default in any Mule version. + +*Issue ID* + +* W- +<.^|`mule.tlsStores.filesystemLookup.enable` +|If enabled, `keyStore`, `clientKeyStore`, and `trustStore` are searched for in the file system, assuming their values are file paths. By default, Mule attempts to load them only as resources within the deployable artifact. + +*Available Since* + +* 4.10.0 + +*Enabled by Default Since* + +* Not enabled by default in any Mule version. + +*Issue ID* + +* W- +<.^|`mule.tlsConf.artifactClassloaderLookup.enable` +|If enabled, the TLS configuration file (for example, `tls-default.conf`) is searched for in the deployable artifact classloader before the Mule distribution `conf` folder. By default, Mule attempts to load it only from the Mule distribution `conf` folder. + +*Available Since* + +* 4.10.0 + +*Enabled by Default Since* + +* Not enabled by default in any Mule version. + +*Issue ID* + +* W- |=== == See Also From 293cfb7a68f406efed7a3732e4de6d8d09b0ab37 Mon Sep 17 00:00:00 2001 From: Daniela Merlo Date: Fri, 19 Sep 2025 13:31:56 -0300 Subject: [PATCH 24/33] W-19420663-applying further feedback --- .../ROOT/pages/mule-troubleshooting-plugin.adoc | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/modules/ROOT/pages/mule-troubleshooting-plugin.adoc b/modules/ROOT/pages/mule-troubleshooting-plugin.adoc index 5331e30cb..e5e680b3b 100644 --- a/modules/ROOT/pages/mule-troubleshooting-plugin.adoc +++ b/modules/ROOT/pages/mule-troubleshooting-plugin.adoc @@ -13,9 +13,9 @@ This Java-based plugin provides an extensible, environment-agnostic solution tha Before using the plugin, make sure that you have these prerequisites: -* Mule runtime distribution starting with 4.10, with patches available for 4.6 and 4.9. +* Supported Mule runtime distributions include version 4.10 and later, or LTS versions 4.9 (with patch 4.9.10 or later) and 4.6 (with patch 4.6.23 or later). * Java 8 or later, matching the Mule runtime version requirements. -* Access to `$MULE_HOME`. The CLI script `diag` automatically locates the Mule home directory. +* Access to the `$MULE_HOME` directory. The CLI script `diag` automatically locates the Mule home directory. The plugin works out-of-the-box in the Standalone and CloudHub deployment models without installing additional dependencies. @@ -31,7 +31,7 @@ The plugin's help output lists the available commands and options. [source,bash] ---- -➜ mule-enterprise-standalone-4.6.21-SNAPSHOT ./tools/diag help +➜ mule-enterprise-standalone-4.6.23 ./tools/diag help Mule Troubleshooting Tool ========================= @@ -174,9 +174,9 @@ This section shows details about the environment where the Mule runtime instance [[diaf-statistics]] === Statistics -This section shows detailed statistics information about deployed Mule applications and their performance metrics. Metrics reflect the runtime state since the last start or redeployment. They reset after redeployments and don't capture complete historical data. Don't use these metrics for pricing or commercial purposes, as they provide a snapshot of runtime behavior. +This section shows detailed statistics information about deployed Mule applications and their performance metrics. Metrics reflect the runtime state since the last start or redeployment. They reset after redeployments and don't capture complete historical data. Note that this information represents a snapshot, or point in time, of the runtime behavior and can differ from the information in the Anypoint Platform usage report, which reflects a period of time. -Set the property `mule.enable.statistics` to collect General Application Metrics and Flow Statistics. +Set the `mule.enable.statistics` system property to collect General Application Metrics and Flow Statistics. ==== Flow Summary Statistics @@ -355,7 +355,7 @@ at [componentId]@[componentLocation]([muleFileName]:[muleFileLineNumber]) [timeI [[diaf-schedulers]] === Schedulers -This section shows the status and metrics of schedulers provided by the xref:scheduler-concept.adoc[scheduler] service, not the source components themselves. For Mule runtime instances with multiple deployed applications, entries are grouped by application. +This section shows the status and metrics of schedulers provided by the scheduler service, which the Mule runtime manages internally, not the xref:scheduler-concept.adoc[source components] themselves. For Mule runtime instances with multiple deployed applications, entries are grouped by application. [cols="1,3", options="header"] |=== @@ -394,7 +394,7 @@ a| Type of tasks the scheduler runs: == Technical Considerations * DIAF provides investigation hints. Check the logs for complete details. -* Heap dumps can contain sensitive data. Enable `--extended` only in secure environments. +* Heap dumps can contain sensitive data. Enable the `--extended` option only in secure environments. * In Mule runtime instances with multiple applications, DIAF sections are grouped by application. == Best Practices @@ -402,4 +402,4 @@ a| Type of tasks the scheduler runs: * Use DIAF for initial troubleshooting before collecting heap or thread dumps manually. * Correlate events in the event dump section with logs by using the `eventId` for deeper analysis. * Collect scheduled diagnostics during maintenance windows in production environments. -* To verify if all the hosts defined in your deployable artifacts (domains, applications, policies) support TLS 1.2 and 1.3 connectivity, enable `mule.extractConnectionData.enable`. On UNIX, the tool generates `_tls_results.csv` along with DIAF output. Enable `mule.extractConnectionData.silentErrors` to log errors without failing deployment. Not available for Windows. +* To verify if all the hosts defined in your deployable artifacts (domains, applications, policies) support TLS 1.2 and 1.3 connectivity, enable the `mule.extractConnectionData.enable` system property. On UNIX, the tool generates `_tls_results.csv` along with DIAF output. Enable the `mule.extractConnectionData.silentErrors` system property to log errors without failing deployment. Not available for Windows. From ad3f384be3777f82b00c759620372661d861f738 Mon Sep 17 00:00:00 2001 From: Daniela Merlo Date: Wed, 24 Sep 2025 13:59:33 -0300 Subject: [PATCH 25/33] w-19450029-update --- modules/ROOT/pages/feature-flagging.adoc | 85 ++---------------------- 1 file changed, 4 insertions(+), 81 deletions(-) diff --git a/modules/ROOT/pages/feature-flagging.adoc b/modules/ROOT/pages/feature-flagging.adoc index e91a4afe8..8a8f0378e 100644 --- a/modules/ROOT/pages/feature-flagging.adoc +++ b/modules/ROOT/pages/feature-flagging.adoc @@ -93,10 +93,6 @@ The following table shows the available feature flags, a description of their fu * 4.5.0 -* 4.4.1 - -* 4.3.1 - *Issue ID* * MULE-19919 @@ -201,8 +197,6 @@ The following table shows the available feature flags, a description of their fu *Enabled by Default Since* -* 4.4.0 - * 4.3.0 *Issue ID* @@ -529,9 +523,7 @@ This feature isn't configurable by system property. *Enabled by Default Since* -* 4.5.0 -* 4.4.0-202210 -* 4.3.0-202210 +* Enabled by default in any Mule version *Issue ID* @@ -573,17 +565,7 @@ This feature isn't configurable by system property. *Enabled by Default Since* -* 4.5.0 - -* 4.4.0 - -* 4.3.0 - -* 4.2.0 - -* 4.1.0 - -* 4.0.0 +* Enabled by default in any Mule version *Issue ID* @@ -614,7 +596,7 @@ This feature isn't configurable by system property. *Enabled by Default Since* -* 4.5.0 +* Not enabled by default in any Mule version *Issue ID* @@ -811,70 +793,11 @@ This feature isn't configurable by system property. *Enabled by Default Since* -* 4.10.0 +* Not enabled by default in any Mule version *Issue ID* * W-18716253 -<.^|`mule.disable.optimised.notification.handler.dynamic.resolution.update.based.on.delegate` -|When disabled, dynamic resolution of notification handling doesn't occur after the Mule artifact initializes. This can result in race conditions that affect monitoring metrics. - -*Available Since* - -* 4.10.0 - -*Enabled by Default Since* - -* Not enabled by default in any Mule version. - -*Issue ID* - -* W- -<.^|`mule.gracefulShutdown.defaultTimeout` -|Sets the default graceful shutdown time for an application in milliseconds. Mule uses this value only if `shutdownTimeout` isn't set in the application configuration. If this default isn't set, the default is 5000 milliseconds. - -*Available Since* - -* 4.10.0 -* 4.9.5 -* 4.6.17 -* 4.4.0-20250530 - -*Enabled by Default Since* - -* Not enabled by default in any Mule version. - -*Issue ID* - -* W- -<.^|`mule.tlsStores.filesystemLookup.enable` -|If enabled, `keyStore`, `clientKeyStore`, and `trustStore` are searched for in the file system, assuming their values are file paths. By default, Mule attempts to load them only as resources within the deployable artifact. - -*Available Since* - -* 4.10.0 - -*Enabled by Default Since* - -* Not enabled by default in any Mule version. - -*Issue ID* - -* W- -<.^|`mule.tlsConf.artifactClassloaderLookup.enable` -|If enabled, the TLS configuration file (for example, `tls-default.conf`) is searched for in the deployable artifact classloader before the Mule distribution `conf` folder. By default, Mule attempts to load it only from the Mule distribution `conf` folder. - -*Available Since* - -* 4.10.0 - -*Enabled by Default Since* - -* Not enabled by default in any Mule version. - -*Issue ID* - -* W- |=== == See Also From f75c8c441f47ba887c85c50c8d9d43557d620874 Mon Sep 17 00:00:00 2001 From: Daniela Merlo Date: Wed, 24 Sep 2025 15:45:36 -0300 Subject: [PATCH 26/33] w-19450029-another update --- modules/ROOT/pages/feature-flagging.adoc | 16 ---------------- 1 file changed, 16 deletions(-) diff --git a/modules/ROOT/pages/feature-flagging.adoc b/modules/ROOT/pages/feature-flagging.adoc index 8a8f0378e..c2aaa3185 100644 --- a/modules/ROOT/pages/feature-flagging.adoc +++ b/modules/ROOT/pages/feature-flagging.adoc @@ -765,22 +765,6 @@ This feature isn't configurable by system property. *Issue ID* * W-16941297 -<.^|`USE_SEPARATE_CLASSLOADER_FOR_POLICY_ISOLATION_PROPERTY` -|When enabled, policy isolation uses a dedicated classloader environment, separate from the domain's, to avoid dependency conflicts. This setup ensures that policies run with their own set of dependencies. - -*Available Since* - -* 4.10.0 -* 4.9.5 -* 4.6.17 - -*Enabled by Default Since* - -* 4.10.0 - -*Issue ID* - -* W-17340911 <.^|`mule.repeatableStreaming.bytes.eagerRead` |When enabled, the `read` methods of bytes repeatable streams return immediately with any available data. If disabled, they don't return until the requested `len` is fully read. Set this property to true to process SSE events over HTTP as they arrive instead of buffering them. From 13c8da944ca8f562b0e95a1ad820b467858081af Mon Sep 17 00:00:00 2001 From: Daniela Merlo <97902112+dmerlob@users.noreply.github.com> Date: Thu, 25 Sep 2025 12:49:10 -0300 Subject: [PATCH 27/33] Update modules/ROOT/pages/mule-troubleshooting-plugin.adoc --- modules/ROOT/pages/mule-troubleshooting-plugin.adoc | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/modules/ROOT/pages/mule-troubleshooting-plugin.adoc b/modules/ROOT/pages/mule-troubleshooting-plugin.adoc index e5e680b3b..1f9d63ba1 100644 --- a/modules/ROOT/pages/mule-troubleshooting-plugin.adoc +++ b/modules/ROOT/pages/mule-troubleshooting-plugin.adoc @@ -391,14 +391,11 @@ a| Type of tasks the scheduler runs: | Number of tasks throttled because the scheduler is at capacity. Shows throttles in the last 1, 5, 15, and 60 minutes. If there aren't any in those intervals, the alert isn't shown. |=== -== Technical Considerations +== Considerations * DIAF provides investigation hints. Check the logs for complete details. * Heap dumps can contain sensitive data. Enable the `--extended` option only in secure environments. * In Mule runtime instances with multiple applications, DIAF sections are grouped by application. - -== Best Practices - * Use DIAF for initial troubleshooting before collecting heap or thread dumps manually. * Correlate events in the event dump section with logs by using the `eventId` for deeper analysis. * Collect scheduled diagnostics during maintenance windows in production environments. From ce07d6e729847650873d4f862f114e77c784b172 Mon Sep 17 00:00:00 2001 From: Daniela Merlo Date: Thu, 25 Sep 2025 14:25:18 -0300 Subject: [PATCH 28/33] w-19450029-applying dev comments --- modules/ROOT/pages/feature-flagging.adoc | 24 ++++++++++++++++++++---- 1 file changed, 20 insertions(+), 4 deletions(-) diff --git a/modules/ROOT/pages/feature-flagging.adoc b/modules/ROOT/pages/feature-flagging.adoc index c2aaa3185..bf50be76b 100644 --- a/modules/ROOT/pages/feature-flagging.adoc +++ b/modules/ROOT/pages/feature-flagging.adoc @@ -243,9 +243,9 @@ The following table shows the available feature flags, a description of their fu * 4.5.0 -* 4.4.0-20220221 +* 4.4.0-20220124 -* 4.3.0-20220221 +* 4.3.0-20220124 *Enabled by Default Since* @@ -327,11 +327,11 @@ Suppressed errors are treated as underlying causes that can also be matched by O *Available Since* -* 4.4.0-20211227 +* 4.5.0 *Enabled by Default Since* -* Not enabled by default in any Mule version. +* 4.5.0 *Issue ID* @@ -754,6 +754,7 @@ This feature isn't configurable by system property. *Available Since* +* 4.10.0 * 4.9.2 * 4.6.14 * 4.4.0-20250217 @@ -782,6 +783,21 @@ This feature isn't configurable by system property. *Issue ID* * W-18716253 +<.^|`mule.disable.optimised.notification.handler.dynamic.resolution.update.based.on.delegate` +|When disabled, dynamic resolution of notification handling doesn't occur after the Mule artifact is initialized. This can cause race conditions that affect monitoring metrics. + +*Available Since* + +* 4.10.0 + +*Enabled by Default Since* + +* Not enabled by default in any Mule version + +*Issue ID* + +* W-16828516 + |=== == See Also From 9ff6ae37e213c2486a8f498b5b4f648d7168c14d Mon Sep 17 00:00:00 2001 From: Daniela Merlo <97902112+dmerlob@users.noreply.github.com> Date: Thu, 25 Sep 2025 15:59:22 -0300 Subject: [PATCH 29/33] Update modules/ROOT/pages/feature-flagging.adoc Co-authored-by: Cristian Pose <101070178+Crispy-Salesforce@users.noreply.github.com> --- modules/ROOT/pages/feature-flagging.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/ROOT/pages/feature-flagging.adoc b/modules/ROOT/pages/feature-flagging.adoc index bf50be76b..ecdb0e759 100644 --- a/modules/ROOT/pages/feature-flagging.adoc +++ b/modules/ROOT/pages/feature-flagging.adoc @@ -767,7 +767,7 @@ This feature isn't configurable by system property. * W-16941297 <.^|`mule.repeatableStreaming.bytes.eagerRead` -|When enabled, the `read` methods of bytes repeatable streams return immediately with any available data. If disabled, they don't return until the requested `len` is fully read. Set this property to true to process SSE events over HTTP as they arrive instead of buffering them. +|When enabled, the `read` methods of bytes repeatable streams return immediately with any available data. If disabled, they don't return until the requested `len` is fully read. Set this property to `true` to process SSE events over HTTP as they arrive instead of buffering them. *Available Since* From 3459e1a020137e8454a3a673e93ccff7add07f7a Mon Sep 17 00:00:00 2001 From: Leandro Ezequiel Barrios Date: Tue, 30 Sep 2025 13:03:26 -0300 Subject: [PATCH 30/33] Work in progress --- modules/ROOT/nav.adoc | 1 + .../pages/fips-140-3-compliance-support.adoc | 196 ++++++++++++++++++ 2 files changed, 197 insertions(+) create mode 100644 modules/ROOT/pages/fips-140-3-compliance-support.adoc diff --git a/modules/ROOT/nav.adoc b/modules/ROOT/nav.adoc index 9d4aa9b98..a36ba052a 100644 --- a/modules/ROOT/nav.adoc +++ b/modules/ROOT/nav.adoc @@ -57,6 +57,7 @@ include::partial$nav-app-dev.adoc[] * xref:securing.adoc[Security] ** xref:secure-configuration-properties.adoc[Secure Configuration Properties] ** xref:fips-140-2-compliance-support.adoc[FIPS 140-2 Compliance Support] + ** xref:fips-140-3-compliance-support.adoc[FIPS 140-3 Compliance Support] ** xref:setting-up-ldap-provider-for-spring-security.adoc[Configure LDAP Provider for Spring Security] ** xref:component-authorization-using-spring-security.adoc[Component Authorization Using Spring Security] ** xref:tls-configuration.adoc[TLS Configuration] diff --git a/modules/ROOT/pages/fips-140-3-compliance-support.adoc b/modules/ROOT/pages/fips-140-3-compliance-support.adoc new file mode 100644 index 000000000..0a7240b52 --- /dev/null +++ b/modules/ROOT/pages/fips-140-3-compliance-support.adoc @@ -0,0 +1,196 @@ += FIPS 140-3 Compliance Support +ifndef::env-site,env-github[] +include::_attributes.adoc[] +endif::[] +:keywords: fips, certifications, security, fips-140-3 + +The Mule 4 Runtime can be configured to run in a Federal Information Processing Standard (FIPS) 140-3 certified environment. Note that Mule doesn't run in FIPS security mode by default. There are two requirements: + +* Have a certified cryptography module installed in your Java environment +* Adjust Mule Runtime settings to run in FIPS security mode + +[IMPORTANT] +-- +FIPS 140-3 support is available starting with Mule 4.10.x and requires Java 17 or later. For earlier versions of Mule Runtime, use xref:fips-140-2-compliance-support.adoc[FIPS 140-2 Compliance Support]. +-- + +== Assumptions + +This document assumes that you're familiar with https://csrc.nist.gov/publications/detail/fips/140/3/final[FIPS 140-3], the US government security standard that requires that compliant parties use only cryptographic algorithms and techniques that have been certified by NIST. + +This document provides instructions for using Bouncy Castle 2.0.0, the recommended FIPS 140-3 certified security provider for Mule Runtime. If you choose to use a different https://csrc.nist.gov/projects/cryptographic-module-validation-program/validated-modules[certified security provider], refer to the documentation specific to your selected provider for configuration instructions. + +[[set_up_environment]] +== Installing Bouncy Castle Security Provider + +Mule Runtime uses Bouncy Castle 2.0.0 as the FIPS 140-3 certified cryptography provider. + +[IMPORTANT] +-- +FIPS 140-3 support requires: + +* Mule 4.10.x or later +* Java 17 or later +* FIPS license from the license `.zip` file provided by MuleSoft (the non-FIPS license isn't valid for FIPS mode) +-- + +=== Installation Steps + +. Verify that you're using Java 17 or later and `JAVA_HOME` is set. +. Download the Bouncy Castle 2.0.0 provider files from https://www.bouncycastle.org/fips-java/[the BouncyCastle web page]. +. Copy the required JAR files to the `$MULE_HOME/lib/boot` folder: ++ +---- +bc-fips-2.0.0.jar +bctls-fips-2.0.19.jar +bcpkix-fips-2.0.7.jar +bcutil-fips-2.0.3.jar +bcpg-fips-2.0.9.jar +bcjmail-fips-2.0.5.jar +---- ++ +. Configure the security providers in the `$JAVA_HOME/conf/security/java.security` file: ++ +---- +security.provider.1=org.bouncycastle.jcajce.provider.BouncyCastleFipsProvider +security.provider.2=org.bouncycastle.jsse.provider.BouncyCastleJsseProvider fips:BCFIPS +security.provider.3=SUN +---- ++ +. Configure the key manager and trust manager algorithms in the same `java.security` file: ++ +---- +ssl.KeyManagerFactory.algorithm=PKIX +ssl.TrustManagerFactory.algorithm=PKIX +---- + +== Running Mule in FIPS Security Mode + +After installing the Bouncy Castle provider, configure Mule to run in FIPS 140-3 mode. + +. Open your `wrapper.conf` file (located in `$MULE_HOME/conf`). +. Add the following properties. Replace `` with the next sequential number in your file: ++ +---- +# Enable FIPS 140-3 security mode +wrapper.java.additional.=-Dmule.security.model=fips140-3 + +# Enable Bouncy Castle approved-only mode +wrapper.java.additional.=-Dorg.bouncycastle.fips.approved_only=true + +# Required for Java 17+ module access +wrapper.java.additional.=--add-opens=java.base/sun.security.provider=org.bouncycastle.fips.core +---- ++ +. If you're using a clustered environment, also add the cluster encryption key: ++ +---- +wrapper.java.additional.=-Dmule.cluster.network.encryption.key={your-encryption-key} +---- ++ +For more information about clustering in FIPS mode, see xref:mule-high-availability-ha-clusters.adoc#cluster_fips[Cluster reference]. ++ +. Save your changes and start Mule runtime. + +[NOTE] +-- +Starting with Mule 4.10.x, BCFKS is the default keystore type, so you don't need to explicitly set `mule.keystore.type=BCFKS` in your `wrapper.conf` file. +-- + +When Mule launches, the startup logs will indicate that FIPS 140-3 security mode is enabled. Mule automatically restricts protocol negotiations to use only approved cryptographic cipher suites. + +[IMPORTANT] +-- +Not all connectors are FIPS 140-3 compliant. Only connectors tagged as "fips-140-3-verified" in Anypoint Exchange are certified for use in FIPS 140-3 environments. Before using any connector in a FIPS 140-3 environment, verify its compliance status in Exchange. +-- + +== FIPS 140-3 Compliant Cipher Suites + +The following cipher suites are enabled by default when running Mule in FIPS 140-3 mode: + +=== TLS 1.3 Cipher Suites + +* TLS_AES_128_GCM_SHA256 +* TLS_AES_256_GCM_SHA384 +* TLS_AES_128_CCM_SHA256 +* TLS_AES_128_CCM_8_SHA256 + +=== TLS 1.2 Cipher Suites + +* TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 +* TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 +* TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 +* TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 +* TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 +* TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 +* TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384 +* TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA +* TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA +* TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA +* TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA + +[NOTE] +-- +These cipher suites are configured in the `$MULE_HOME/conf/tls-fips140-3.conf` file. FIPS 140-3 requires support for TLS 1.3 and TLS 1.2. TLS 1.1 and earlier versions are not supported. +-- + +== FIPS 140-3 Compliant Keystore Formats + +Keystores or truststores in Mule apps are typically formatted as `PKCS12` or `JKS`. These formats aren't FIPS compliant. For compliance, convert them to `BCFKS` format. + +. Download the `bc-fips-2.0.0.jar` file from the https://www.bouncycastle.org/download/bouncy-castle-java-fips/[Bouncy Castle website]. +. Use this example command to convert a keystore to `BCFKS` format: + +---- +BC_FIPS_JAR=${BC_PATH}/bc-fips-2.0.0.jar # Replace with a correct path +OLD_KEYSTORE="keystore.jks" # Replace with the keystore to convert +OLD_PASSWD="changeit" # Replace with the keystore password +NEW_KEYSTORE="keystore.bcfks" # Replace with the new keystore +NEW_PASSWD="changeit" # Replace with the new keystore password + +keytool -importkeystore \ + -providerclass org.bouncycastle.jcajce.provider.BouncyCastleFipsProvider \ + -providerpath ${BC_FIPS_JAR} \ + -srckeystore ${OLD_KEYSTORE} -srcstoretype JKS -srcstorepass ${OLD_PASSWD} \ + -destkeystore ${NEW_KEYSTORE} -deststoretype BCFKS -deststorepass ${NEW_PASSWD} +---- +[NOTE] +-- +If the source keystore is `PKCS12`, set the parameter `-srcstoretype` to `PKCS12` in the `keytool` command. +-- +[start=4] +. To use the new keystore or truststore, update the xref:tls-configuration.adoc[TLS configuration] in the Mule configuration file: + +---- + + + + +---- + +== Connector Compatibility + +[IMPORTANT] +-- +Only connectors tagged as "fips-140-3-verified" in Anypoint Exchange are certified for FIPS 140-3 environments. Verify connector compliance before deploying: + +. Go to Anypoint Exchange +. Search for the connector +. Check for the "fips-140-3-verified" tag +-- + +== Tips and Limitations + +* Not all encryption schemes and signatures are FIPS 140-3 compliant. If your application uses a non-approved algorithm, you will get an error at runtime: +.... + Could not find encryption algorithm ''. + You are running in FIPS mode, so please verify that + the algorithm is compliant with FIPS. +.... +* Different environments may have different security configurations. Test thoroughly before deploying to production. + +== See Also + +* https://csrc.nist.gov/projects/cryptographic-module-validation-program/validated-modules[Validated FIPS-3 Cryptographic Modules] +* https://csrc.nist.gov/publications/detail/fips/140/3/final[FIPS 140-3 Standard] +* xref:fips-140-2-compliance-support.adoc[FIPS 140-2 Compliance Support] From 04495ce982a0493d21b946acaf804d117c6aa878 Mon Sep 17 00:00:00 2001 From: Daniela Merlo Date: Tue, 30 Sep 2025 17:54:46 -0300 Subject: [PATCH 31/33] W-19785676-doc edited --- .../pages/fips-140-3-compliance-support.adoc | 81 +++++++++---------- 1 file changed, 39 insertions(+), 42 deletions(-) diff --git a/modules/ROOT/pages/fips-140-3-compliance-support.adoc b/modules/ROOT/pages/fips-140-3-compliance-support.adoc index 0a7240b52..35c65c8d4 100644 --- a/modules/ROOT/pages/fips-140-3-compliance-support.adoc +++ b/modules/ROOT/pages/fips-140-3-compliance-support.adoc @@ -4,40 +4,40 @@ include::_attributes.adoc[] endif::[] :keywords: fips, certifications, security, fips-140-3 -The Mule 4 Runtime can be configured to run in a Federal Information Processing Standard (FIPS) 140-3 certified environment. Note that Mule doesn't run in FIPS security mode by default. There are two requirements: +Configure Mule 4 to run in a Federal Information Processing Standard (FIPS) 140-3 certified environment. -* Have a certified cryptography module installed in your Java environment -* Adjust Mule Runtime settings to run in FIPS security mode +Mule doesn't run in FIPS security mode by default. To enable it, you must: -[IMPORTANT] --- -FIPS 140-3 support is available starting with Mule 4.10.x and requires Java 17 or later. For earlier versions of Mule Runtime, use xref:fips-140-2-compliance-support.adoc[FIPS 140-2 Compliance Support]. --- +* Install a certified cryptography module in your Java environment +* Adjust Mule runtime settings to run in FIPS security mode + +== Compatibility + +FIPS 140-3 support requires: + +* Mule 4.10 or later ++ +For earlier versions of Mule runtime, use xref:fips-140-2-compliance-support.adoc[FIPS 140-2 Compliance Support]. +* Java 17 or later +* FIPS license from the license `.zip` file provided by MuleSoft (the non-FIPS license isn't valid for FIPS mode) == Assumptions -This document assumes that you're familiar with https://csrc.nist.gov/publications/detail/fips/140/3/final[FIPS 140-3], the US government security standard that requires that compliant parties use only cryptographic algorithms and techniques that have been certified by NIST. +This document assumes you're familiar with https://csrc.nist.gov/publications/detail/fips/140/3/final[FIPS 140-3], the US government security standard that requires that compliant parties use only cryptographic algorithms and techniques that have been certified by NIST. -This document provides instructions for using Bouncy Castle 2.0.0, the recommended FIPS 140-3 certified security provider for Mule Runtime. If you choose to use a different https://csrc.nist.gov/projects/cryptographic-module-validation-program/validated-modules[certified security provider], refer to the documentation specific to your selected provider for configuration instructions. +These instructions use Bouncy Castle 2.0.0, the recommended FIPS 140-3 certified security provider for Mule runtime. If you use a different https://csrc.nist.gov/projects/cryptographic-module-validation-program/validated-modules[certified security provider], refer to that provider's documentation for configuration instructions. [[set_up_environment]] == Installing Bouncy Castle Security Provider -Mule Runtime uses Bouncy Castle 2.0.0 as the FIPS 140-3 certified cryptography provider. - -[IMPORTANT] --- -FIPS 140-3 support requires: - -* Mule 4.10.x or later -* Java 17 or later -* FIPS license from the license `.zip` file provided by MuleSoft (the non-FIPS license isn't valid for FIPS mode) --- +Mule runtime uses Bouncy Castle 2.0.0 as its FIPS 140-3 certified cryptography provider. === Installation Steps +These instructions show how to install and configure Bouncy Castle security provider in Java 17 or later. + . Verify that you're using Java 17 or later and `JAVA_HOME` is set. -. Download the Bouncy Castle 2.0.0 provider files from https://www.bouncycastle.org/fips-java/[the BouncyCastle web page]. +. Download the Bouncy Castle 2.0.0 provider files from https://www.bouncycastle.org/fips-java/[the BouncyCastle website]. . Copy the required JAR files to the `$MULE_HOME/lib/boot` folder: + ---- @@ -66,10 +66,10 @@ ssl.TrustManagerFactory.algorithm=PKIX == Running Mule in FIPS Security Mode -After installing the Bouncy Castle provider, configure Mule to run in FIPS 140-3 mode. +After installing the Bouncy Castle provider, configure Mule to run in FIPS 140-3 mode: . Open your `wrapper.conf` file (located in `$MULE_HOME/conf`). -. Add the following properties. Replace `` with the next sequential number in your file: +. Add these properties. Replace `` with the next sequential number in your file: + ---- # Enable FIPS 140-3 security mode @@ -94,19 +94,19 @@ For more information about clustering in FIPS mode, see xref:mule-high-availabil [NOTE] -- -Starting with Mule 4.10.x, BCFKS is the default keystore type, so you don't need to explicitly set `mule.keystore.type=BCFKS` in your `wrapper.conf` file. +Starting with Mule 4.10, BCFKS is the default keystore type. Setting `mule.keystore.type=BCFKS` in your `wrapper.conf` file isn't required. -- -When Mule launches, the startup logs will indicate that FIPS 140-3 security mode is enabled. Mule automatically restricts protocol negotiations to use only approved cryptographic cipher suites. +When Mule launches, the startup logs show that FIPS 140-3 security mode is enabled. Mule automatically restricts protocol negotiations to use only approved cryptographic cipher suites. [IMPORTANT] -- -Not all connectors are FIPS 140-3 compliant. Only connectors tagged as "fips-140-3-verified" in Anypoint Exchange are certified for use in FIPS 140-3 environments. Before using any connector in a FIPS 140-3 environment, verify its compliance status in Exchange. +Not all connectors are FIPS 140-3 compliant. Only connectors tagged as `fips-140-3-verified` in Anypoint Exchange are certified to use in FIPS 140-3 environments. Always verify compliance in Exchange before deploying. -- == FIPS 140-3 Compliant Cipher Suites -The following cipher suites are enabled by default when running Mule in FIPS 140-3 mode: +These cipher suites are enabled by default when running Mule in FIPS 140-3 mode. === TLS 1.3 Cipher Suites @@ -131,12 +131,12 @@ The following cipher suites are enabled by default when running Mule in FIPS 140 [NOTE] -- -These cipher suites are configured in the `$MULE_HOME/conf/tls-fips140-3.conf` file. FIPS 140-3 requires support for TLS 1.3 and TLS 1.2. TLS 1.1 and earlier versions are not supported. +These cipher suites are configured in the `$MULE_HOME/conf/tls-fips140-3.conf` file. FIPS 140-3 requires support for TLS 1.3 and TLS 1.2. Earlier TLS versions aren't supported. -- == FIPS 140-3 Compliant Keystore Formats -Keystores or truststores in Mule apps are typically formatted as `PKCS12` or `JKS`. These formats aren't FIPS compliant. For compliance, convert them to `BCFKS` format. +Keystores or truststores in Mule apps are usually formatted as `PKCS12` or `JKS`. These formats aren't FIPS compliant. For compliance, convert them to `BCFKS` format: . Download the `bc-fips-2.0.0.jar` file from the https://www.bouncycastle.org/download/bouncy-castle-java-fips/[Bouncy Castle website]. . Use this example command to convert a keystore to `BCFKS` format: @@ -154,12 +154,12 @@ keytool -importkeystore \ -srckeystore ${OLD_KEYSTORE} -srcstoretype JKS -srcstorepass ${OLD_PASSWD} \ -destkeystore ${NEW_KEYSTORE} -deststoretype BCFKS -deststorepass ${NEW_PASSWD} ---- + [NOTE] --- -If the source keystore is `PKCS12`, set the parameter `-srcstoretype` to `PKCS12` in the `keytool` command. --- +If the source keystore is `PKCS12`, set `-srcstoretype` to `PKCS12` in the `keytool` command. + [start=4] -. To use the new keystore or truststore, update the xref:tls-configuration.adoc[TLS configuration] in the Mule configuration file: +. Update the xref:tls-configuration.adoc[TLS configuration] in the Mule configuration file to use the new keystore or truststore: ---- @@ -168,26 +168,23 @@ If the source keystore is `PKCS12`, set the parameter `-srcstoretype` to `PKCS12 ---- -== Connector Compatibility +== Connectors Compatibility -[IMPORTANT] --- -Only connectors tagged as "fips-140-3-verified" in Anypoint Exchange are certified for FIPS 140-3 environments. Verify connector compliance before deploying: +Only connectors tagged as `fips-140-3-verified` in Anypoint Exchange are certified for use in FIPS 140-3 environments. To check compliance in Exchange before deploying: -. Go to Anypoint Exchange -. Search for the connector -. Check for the "fips-140-3-verified" tag --- +. Open Anypoint Exchange. +. Search for the connector. +. Check for the `fips-140-3-verified` tag. == Tips and Limitations -* Not all encryption schemes and signatures are FIPS 140-3 compliant. If your application uses a non-approved algorithm, you will get an error at runtime: +* Not all encryption schemes and signatures are FIPS 140-3 compliant. If your app uses a non-approved algorithm, you get this runtime error: .... Could not find encryption algorithm ''. You are running in FIPS mode, so please verify that the algorithm is compliant with FIPS. .... -* Different environments may have different security configurations. Test thoroughly before deploying to production. +* Different environments can have different security configurations. Test before deploying to production. == See Also From 29c6a21724c4b5f5a1231b365deaf8faaae99218 Mon Sep 17 00:00:00 2001 From: Daniela Merlo <97902112+dmerlob@users.noreply.github.com> Date: Wed, 1 Oct 2025 10:24:40 -0300 Subject: [PATCH 32/33] Update modules/ROOT/pages/fips-140-3-compliance-support.adoc Co-authored-by: melissa-kulm-sfdc1 --- modules/ROOT/pages/fips-140-3-compliance-support.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/ROOT/pages/fips-140-3-compliance-support.adoc b/modules/ROOT/pages/fips-140-3-compliance-support.adoc index 35c65c8d4..427794601 100644 --- a/modules/ROOT/pages/fips-140-3-compliance-support.adoc +++ b/modules/ROOT/pages/fips-140-3-compliance-support.adoc @@ -17,7 +17,7 @@ FIPS 140-3 support requires: * Mule 4.10 or later + -For earlier versions of Mule runtime, use xref:fips-140-2-compliance-support.adoc[FIPS 140-2 Compliance Support]. +For earlier versions of Mule runtime, use xref:fips-140-2-compliance-support.adoc[FIPS 140-2 Compliance Support] which requires: * Java 17 or later * FIPS license from the license `.zip` file provided by MuleSoft (the non-FIPS license isn't valid for FIPS mode) From 13fe6cb7cafe4fce00b1e257c3832578adc93243 Mon Sep 17 00:00:00 2001 From: Daniela Merlo <97902112+dmerlob@users.noreply.github.com> Date: Wed, 1 Oct 2025 10:25:06 -0300 Subject: [PATCH 33/33] Update modules/ROOT/pages/fips-140-3-compliance-support.adoc --- modules/ROOT/pages/fips-140-3-compliance-support.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/modules/ROOT/pages/fips-140-3-compliance-support.adoc b/modules/ROOT/pages/fips-140-3-compliance-support.adoc index 427794601..94758c581 100644 --- a/modules/ROOT/pages/fips-140-3-compliance-support.adoc +++ b/modules/ROOT/pages/fips-140-3-compliance-support.adoc @@ -8,8 +8,8 @@ Configure Mule 4 to run in a Federal Information Processing Standard (FIPS) 140- Mule doesn't run in FIPS security mode by default. To enable it, you must: -* Install a certified cryptography module in your Java environment -* Adjust Mule runtime settings to run in FIPS security mode +* Install a certified cryptography module in your Java environment. +* Adjust Mule runtime settings to run in FIPS security mode. == Compatibility