Configuring routes startup ordering and autostartup

Available as of Camel 2.1

Camel now supports configuring two aspects:

  • auto startup
  • order of starting routes

Configuring whether Camel should be auto started or not in XML DSL

The old option shouldStartContext have been removed and replaced with this new autoStartup option instead. What it allows is to configure Camel to not auto start when Spring starts.

For example the route below we have configured autoStartup=false to prevent Camel starting when Spring starts.

So how do you start Camel then?

The autoStartup option on the <camelContext> is only used once, so you can manually start Camel later by invoking its start method as shown below:

Configuring whether a route should be started or not in XML DSL

You can use the autoStartup option to configure if a given route should be started when Camel starts. By default a route is auto started.

You can disable or enable it as follows:

In XML DSL you define it as follows:

And to explicit state it should be started

Configuring whether a route should be started or not in Java DSL

You can use the autoStartup option to configure if a given route should be started when Camel starts. By default a route is auto started.

You can disable or enable it as follows:

Configuring whether a route should be started or not, using a boolean or String, in Java DSL

Available as of Camel 2.9

To startup based on a boolean, String or Property, do one of the following:

Configuring starting order for routes

You can also configure the order in which routes are started. Previously Camel started the routes in a non deterministic order. Now you have fine grained control in which order the routes should be started. There is a new attribute startupOrder which is a Integer that states the order. Camel then sorts the routes before starting time. The routes with the lowest startupOrder is started first. All startupOrder defined must be unique among all routes in your CamelContext.
You should also use numbers that are lower than 1000, as routes without an explicit startupOrder define will have a number starting from 1000 auto assigned. So view numbers from 1000 upwards as reserved internally for Camel itself.

In terms of the startupOrder there are no strict rule that it must start from 1 and increment by 1. You can for example use: 100, 200, 205, 89 if you like. Only rule of thumb is that the numbers must be unique.

Why do you want to control the starting order?

It can help in cases where routes are inter dependent on each other and also help with graceful shutting down Camel as Camel can stop the routes in the correct order as well.

Stopping routes

Icon

Camel 2.2: Camel will stop the routes in the same order that they were started.
Camel 2.3: Camel will stop the routes in the reverse order that they were started.

Examples

Lets try a couple of examples

Simple example

And the same example with XML DSL:

In this example we have two routes in which we have started that the direct:start route should be started after the seda:foo route.
As direct:start is consider the input and we want that seda:foo route to be up and running beforehand.

You can also mix and match routes with and without startupOrder define.

Routes with startupOrder mixed with routes without

And the same example with XML DSL:

In the route above we have not define a startupOrder on the last route direct:bar in which Camel will auto assign a number for it, in which this case will be 1000. So therefore the route will be started last.

So you can use this to your advantage to only assign a startupOrder on the routes which really needs it.

Shutdown

Camel 2.2: Camel will shutdown the routes in the same order that they were started.
Camel 2.3: Camel will shutdown the routes in the reverse order that they were started.

See also Graceful Shutdown.

See also

© 2004-2014 The Apache Software Foundation.
Apache Camel, Camel, Apache, the Apache feather logo, and the Apache Camel project logo are trademarks of The Apache Software Foundation. All other marks mentioned may be trademarks or registered trademarks of their respective owners.
Graphic Design By Hiram