camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From apara <ap...@standardset.com>
Subject Failed to start route route4 because of startupOrder clash. Route route3 already has startupOrder 498 configured which this route have as well
Date Sat, 02 May 2015 19:27:19 GMT
I am creating a lot of routes dynamically and wanted to make sure that lower
level dependents start first before those routes that depend on them. 
However, I am getting this error:

Failed to start route route4 because of startupOrder clash. Route route3
already has startupOrder 498 configured which this route have as well.
Please correct startupOrder to be unique among all your routes.

I think startupOrder should be interpreted more like a startupPriority. 
Routes at the same startupPriority should start at the same time, however,
if priority of two routes is the same, the startup between those two routes
would be ambiguous.

-AP_




--
View this message in context: http://camel.465427.n5.nabble.com/Failed-to-start-route-route4-because-of-startupOrder-clash-Route-route3-already-has-startupOrder-498l-tp5766591.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Mime
View raw message