Mailing-List: contact issues-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Date: Thu, 15 Sep 2016 16:38:20 +0000 (UTC)
From: "Vladimir Dzalbo (JIRA)" <jira@apache.org>
To: issues@camel.apache.org
Message-ID: <JIRA.13005212.1473957489000.581669.1473957500422@Atlassian.JIRA>
In-Reply-To: <JIRA.13005212.1473957489000@Atlassian.JIRA>
References: <JIRA.13005212.1473957489000@Atlassian.JIRA> <JIRA.13005212.1473957489012@arcas>
Subject: [jira] [Created] (CAMEL-10323) MQTT producer creation fails if
 network is not available at startup
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 15 Sep 2016 16:38:22 -0000

Vladimir Dzalbo created CAMEL-10323:
---------------------------------------

             Summary: MQTT producer creation fails if network is not available at startup
                 Key: CAMEL-10323
                 URL: https://issues.apache.org/jira/browse/CAMEL-10323
             Project: Camel
          Issue Type: Bug
          Components: camel-mqtt
    Affects Versions: 2.17.3, 2.17.2
            Reporter: Vladimir Dzalbo


Trying to use Camel in environment with unstable network came with following problem: when Camel context starts up with network not being available no matter what retry settings are set, the creation of the producer will fail, which will also by default mean failure in the creation of context.

It would be good if behavior was similar to other components (like mina or netty), where producer tries to establish connection when it has a message to send (or periodically?)  

So, once network connection is created (maybe hours or days after creation) endpoint would be functional and all messages can be delivered given  Guaranteed Delivery pattern is used.


Can we avoid fatal exception on creation of the Endpoint?


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)