You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by igarashitm <gi...@git.apache.org> on 2015/08/26 09:10:12 UTC

[GitHub] camel pull request: CAMEL-9092 MQTT consumer receives duplicate me...

GitHub user igarashitm opened a pull request:

    https://github.com/apache/camel/pull/601

    CAMEL-9092 MQTT consumer receives duplicate messages after broker res…

    …tart
    
    Listener.onDisconnect() is also invoked when connection recovery occurs in mqtt-client internally, so it shouldn't attempt to reconnect from outside.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/igarashitm/camel CAMEL-9092

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/camel/pull/601.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #601
    
----
commit c4b2db9ded98f403f9705c4a56cc9c36f7cdad85
Author: Tomohisa Igarashi <tm...@gmail.com>
Date:   2015-08-26T07:03:23Z

    CAMEL-9092 MQTT consumer receives duplicate messages after broker restart
    
    Listener.onDisconnect() is also invoked when connection recovery occurs in mqtt-client internally, so it shouldn't attempt to reconnect from outside.

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] camel pull request: CAMEL-9092 MQTT consumer receives duplicate me...

Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:

    https://github.com/apache/camel/pull/601


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---