I’ve dealt with situations like this using Blueprint reference-listeners.
Basically, I setup a reference listener to start the context when a service
becomes available (or restart the context if the service implementation is
switched). For this to work, I had to write a little code that exposed
Hi Jonathan,
I think we would like to address this with health checks[1], some of
which shipped in 2.19.0 and we would like to improve on this.
Perhaps it would be nice to tie health checks this into control bus
and let the user define a policy on how to handle failures. But this
is somewhat new t
NDI4fDE1MzI5MTE2NTY=>
> .
> NAML
> <http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcr
It looks like it comes from the exception is coming from
the JdbcAggregationRepository, in fact.
2017-05-16 15:39 GMT+02:00 Jonathan Schoreels
:
> Hi all,
>
> It seems that if a database is unreachable, and if the camelcontext
> contains a sql consumer, the camel context won't start, even though
Hi all,
It seems that if a database is unreachable, and if the camelcontext
contains a sql consumer, the camel context won't start, even though marked
as Created in karaf console.
I don't mind the karaf "created" marked, but I would love to know if you
have any advice to startup sql route when th
