There are multiple Camel routes in a SY application. If you have a Camel service binding, for example, that's a route. If the Camel service binding routes into your camel routing service (i.e. a Camel implementation), then the implementation is a route as well. You want to stop the gateway and not the route for the implementation if you want to stop the flow of messages into the service. Rob has a monster commit coming up which adds plumbing, admin, JMX, and console support for starting/stopping gateway bindings. I think this is the best way to achieve what you want in 1.0. For 0.8, if you are using a Camel gateway binding you can always find the gateway route via the CamelContext (one per application) and stop it that way.