---
schema_version: "1"
id: c57a3b9ce8150c9efb6a619a1a93f1c0675f61e653b7be7154b6baa3605578e8
title: Global Configurations
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/mule-runtime/4.3/global-settings-configuration.md
canonical_url: https://docs.mulesoft.com/mule-runtime/4.3/global-settings-configuration
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 247bfbde132636222c5fca31410c40ea96e2e7b18b8ba6ea2d213225e24aaca9
description: MuleSoft Documentation Site
release: "4.3"
latest: false
---
---
product: Mule Runtime
version: 4.3
keywords: configure, finetune, global, global settings
---

# Global Configurations

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

Global configurations for a mule application such as the default transaction timeout or default
error handler can be configured in the `<configuration>` element of the root level of the
[Mule Configuration File](https://docs.mulesoft.com/mule-runtime/4.3/about-mule-configuration).

## Create a Global Configuration from Studio

To create a global configuration:

1.  In Studio, select the **Global Elements** tab and click **Create**:

    ![create-global-settings](/mulesoft/current/en-us/mule-runtime/4.3/_images/mruntime-global-settings-create.png)

2.  Select **Global Configurations** > **Configuration**:

    ![configure-global-settings](/mulesoft/current/en-us/mule-runtime/4.3/_images/mruntime-global-configurations.png)

3.  Configure the **Default Error Handler** and the **HA Profile** values.

## Create a Global Configuration by Editing the XML

The following example defines a global error handler, and then a global configuration that specifies
a default transaction timeout and references the global error handler as the default:

```xml
<mule>
  ...
  <!-- Error handler -->
  <error-handler name="GlobalErrorHandler"/>
  <!-- Global Settings -->
  <configuration doc:name="GlobalSettings" defaultTransactionTimeout="31337" defaultErrorHandler-ref="GlobalErrorHandler" />
  ...
  </configuration>
  ...
</mule>
```

## Global Configurations Reference

The following table shows all attributes of the `<configuration>` element:

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Name</th><th>Type</th><th>Required</th><th>Default</th><th>Description</th></tr></thead><tbody><tr><td><p><code>defaultResponseTimeout</code></p></td><td><p><code>string</code></p></td><td><p>no</p></td><td><p><code>10000</code></p></td><td><p>The default period (ms) to wait for a synchronous response.</p></td></tr><tr><td><p><code>defaultTransactionTimeout</code></p></td><td><p><code>string</code></p></td><td><p>no</p></td><td><p><code>30000</code></p></td><td><p>The default timeout (ms) for transactions. This can also be configured on transactions, in which case the transaction configuration is used instead of this default.</p></td></tr><tr><td><p><code>defaultErrorHandler-ref</code></p></td><td><p><code>string</code></p></td><td><p>no</p></td><td><p>none</p></td><td><p>The default error handler for every flow. This must be a reference to a global error handler.</p></td></tr><tr><td><p><code>shutdownTimeout</code></p></td><td><p><code>integer</code></p></td><td><p>no</p></td><td><p><code>5000</code></p></td><td><p>(As of Mule 2.2.2) The time in milliseconds to wait for any in-progress messages to finish processing before Mule shuts down. After this threshold has been reached, Mule starts interrupting threads, and messages can be lost. If you have a very large number of services in the same Mule instance, if you have components that take more than a couple seconds to process, or if you are using large payloads and/or slower transports, you should increase this value to allow more time for graceful shutdown. The value you specify is applied to services and separately to dispatchers, so the default value of 5000 milliseconds specifies that Mule has ten seconds to process and dispatch messages gracefully after shutdown is initiated.</p></td></tr><tr><td><p><code>maxQueueTransactionFilesSize</code></p></td><td><p><code>integer</code></p></td><td><p>no</p></td><td><p><code>500</code></p></td><td><p>The approximated maximum space in megabytes used by the transaction log files for transactional persistent queues. Take into account that this number applies both to the set of transaction log files for XA and for local transactions. If both type of transactions are used then the approximated maximum space used will be twice the configured value.</p></td></tr><tr><td><p><code>defaultObjectSerializer-ref</code></p></td><td><p><code>string</code></p></td><td><p>no</p></td><td><p>none</p></td><td><p>An optional reference to an ObjectSerializer to be used as the application’s default.</p></td></tr></tbody></table>

### Child Elements of <configuration>

<table><colgroup><col> <col></colgroup><thead><tr><th>Name</th><th>Description</th></tr></thead><tbody><tr><td><p><code>dynamic-config-expiration</code></p></td><td><p>Optional. The default expiration settings for dynamic configurations, used by connectors. This can also be configured on connectors, in which case the connector configuration is used instead of this default.<br>For configuration details, see: <a href="https://docs.mulesoft.com/mule-sdk/latest/static-dynamic-configs#dynamic-config-expiration">Dynamic Configuration Expiration</a>.</p></td></tr><tr><td><p><code>cluster-config</code></p></td><td><p>Optional. Mule application cluster configuration.<br>For configuration details, see: <a href="https://docs.mulesoft.com/on-premises/latest/mule-high-availability-ha-clusters#cluster-high-performance">Clustering for High Performance</a>.</p></td></tr></tbody></table>

## See Also

- [Error Handling](https://docs.mulesoft.com/mule-runtime/4.3/error-handling)

- [Dynamic Configurations](https://docs.mulesoft.com/mule-sdk/latest/static-dynamic-configs)

- [Mule High Availability Cluster](https://docs.mulesoft.com/on-premises/latest/mule-high-availability-ha-clusters)