Nav
You are viewing an older version of this section. Click here to navigate to the latest version.

Global Settings Configuration Reference

This page provides details on the global settings you configure at the root level of a Mule configuration. For more information on configuration, see About Mule Configuration. For information on threading profiles, see Tuning Performance.

Configuration

Specifies defaults and general settings for the Mule instance.

Attributes of configuration

Name Description

defaultResponseTimeout

The default period (ms) to wait for a synchronous response.
Type: string
Required: no
Default: 10000

defaultTransactionTimeout

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.
Type: string
Required: no
Default: 30000

defaultExceptionStrategy-ref

The default exception strategy for every flow / service. This must be a reference to a global exception strategy.
Type: string
Required: no
Default: none

shutdownTimeout

(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.
Type: integer
Required: no
Default: 5000

useExtendedTransformations

Backwards Compatabilty Flag: Used to disable the new extended transformation support introduced in Mule 3.3 including enforcement of transformations, implicit transformations and no direct transformer lookup.
Type: boolean
Required: no
Default: true

flowEndingWithOneWayEndpointReturnsNull

Backwards Compatabilty Flag: Used to revert to Mule 3.2 behavior of one-way outbound endpoints when they are the last element inside a request-response flow. When true, the value returned by the endpoint is null, otherwise it’s an echo of the received event.
Type: boolean
Required: no
Default: false

enricherPropagatesSessionVariableChanges

Backwards Compatabilty Flag: Used to revert to Mule 3.1/3.2 behavior of the message enricher so that session variables added or modified within an enricher are propagated up into the flow where the enricher is used.
Type: boolean
Required: no
Default: false

defaultObjectSerializer-ref

An optional reference to an ObjectSerializer to be used as the application’s default.
Type: string
Required: no
Default: none

defaultProcessingStrategy

The default processing strategy to use in all flows which don’t specify otherwise.
Type: flowProcessingStrategyType
Required: no
Default: none

Child Elements of <configuration…​>

Name Cardinality Description

default-threading-profile

0..1

The default threading profile, used by components and by endpoints for dispatching and receiving if no more specific configuration is given.

default-dispatcher-threading-profile

0..1

The default dispatching threading profile, which modifies the default-threading-profile values and is used by endpoints for dispatching messages. This can also be configured on connectors, in which case the connector configuration is used instead of this default.

default-receiver-threading-profile

0..1

The default receiving threading profile, which modifies the default-threading-profile values and is used by endpoints for receiving messages. This can also be configured on connectors, in which case the connector configuration is used instead of this default.

default-service-threading-profile

0..1

The default service threading profile, which modifies the default-threading-profile and is used by services for processing messages. This can also be configured on models or services, in which case these configurations are used instead of this default.

abstract-reconnection-strategy

0..1

The default reconnection strategy, used by connectors and endpoints. This can also be configured on connectors, in which case the connector configuration is used instead of this default. A placeholder for a reconnection strategy element. Reconnection strategies define how Mule should attempt to handle a connection failure.

expression-language

0..1

Configuration of Mule Expression Language

abstract-configuration-extension

0..*

Mule application configuration extensions. Extensions can be defined as child of the configuration elements and then accessed by each module that defines it. A placeholder for arbitrary extensions as children of the 'configuration' element. Other transports and modules can extend this if they need to add elements to the configuration.

In this topic: