Hi David,
The camel mqtt component does not implement the "ReconnectAttempts"
parameters of the mqtt-client (
https://github.com/fusesource/mqtt-client#controlling-connection-reconnects).
Can you please raise a ticket to request to improve the client please ?
Regards,
On Tue, Oct 14, 2014 at 5:44 PM, ddewaele <ddewa...@gmail.com> wrote:
> We're using the MQTT endpoint end noticed that when there is a transport
> failure the endpoint simply disconnects the connection but never connects
> again.
>
> Attempting to publish messages using this endpoint results in a failure :
> java.lang.IllegalStateException: Disconnected
>
> Is this by design or is there something we can do to alter this behavior ?
> Shouldn't the endpoint attempt to reconnect in this case ?
>
> public void onFailure(Throwable value) {
> connection.disconnect(new Callback<Void>() {
> public void onSuccess(Void value) {
> }
>
> public void onFailure(Throwable e) {
> LOG.debug("Failed to disconnect from " +
> configuration.getHost() + ". This exception is ignored.", e);
> }
> });
> }
>
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Camel-MQTT-Endpoint-reconnect-on-transport-failure-tp5757564.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
--
Charles Moulliard
Apache Committer / Architect @RedHat
Twitter : @cmoulliard | Blog : http://cmoulliard.github.io
