We encountered a very strange behavior. In our camel app we set the id of all routes via "setId(id)". This is working fine so far. One of our route builders generates n routes in a for loop and uses <Prefix>+<EndUri> as route id. Here set Route is called on a ThrottleDefinition.
This is working fin on mot of our machines (all developer machines, test, and pre-life) but on production those n routes get names like route-1...route-n (default camel names). I don't have any clue why this difference. Can someone please give a hint where to look? Or how to fix it? -- View this message in context: http://camel.465427.n5.nabble.com/naming-routes-with-setId-doesn-t-work-on-a-specific-machine-tp5754365.html Sent from the Camel - Users mailing list archive at Nabble.com.
