Contact Free trial Login

Jetty Transport

Mule Runtime Engine versions 3.5, 3.6, and 3.7 reached End of Life on or before January 25, 2020. For more information, contact your Customer Success Manager to determine how you can migrate to the latest Mule version.

The Jetty transport provides support for exposing applications over HTTP by embedding a light-weight Jetty server. The Jetty SSL Transport works the same way but over SSL. You can only define inbound endpoints with this transport.

The Javadoc for this transport can be found below:

The connector allows Mule to expose Mule Services over HTTP using a Jetty HTTP server. A single Jetty server is created for each connector instance. One connector can serve many endpoints. Users should rarely need to have more than one Jetty connector. The Jetty connector can be configured using a Jetty XML config file, but the default configuration is sufficient for most scenarios.

Attributes of the Connector

These attributes are for the optional global connector, jetty:connector.

Name Description


The name of the connector that can be referenced in a flow.

Type: string
Required: yes
Default: Jetty


The location of the Jetty config file to configure this connector with.

Type: string
Required: no
Default: none


The number of acceptor threads.

Type: integer
Required: no
Default: 1


Specifies a local path where files are served from. The local path gets mapped directly to the path on the 'serverUrl'.

Type: string
Required: no
Default: none


Whether to use continuations to free up connections in high load situations.

Type: boolean
Required: no
Default: none


A descriptive name for the connector. Not required in Mule Standalone configuration.

Type: string
Required: Only for Studio configurations
Default: Jetty

Child Elements of the Connector

Name Cardinality Description



Allows configuring of a directory which contains WAR files to be served out by Jetty.


Jetty endpoints are configured the same way as FTP endpoints. Note that the Jetty transport can only be used for inbound endpoints.

For example:

<?xml version="1.0" encoding="UTF-8"?>
<mule xmlns:jetty="" xmlns:file="" xmlns="" xmlns:doc=""
    <flow name="somethingFlow1" doc:name="somethingFlow1">
        <jetty:inbound-endpoint exchange-pattern="request-response" address="http://localhost:8081/path" doc:name="Jetty"/>

Was this article helpful?

💙 Thanks for your feedback!

Edit on GitHub