Re: [mosquitto-dev] Mosquitto c++ lib unexpected disconnect.

["Sunderman, Adam" <Adam.Sunderman@xxxxxxxxxxxx>]

Hi Roger,

I just wanted to touch base on this issue. Basically, don't sweat it. I have discovered that the network interface was pulled out right from under us. It came back, but our mosquitto instance was left in the cold and didn't handle recovery.

Your insight actually allowed me to fix a few other issues while investigating this one!

Thanks for your help,
Adam
________________________________________
From: mosquitto-dev-bounces@xxxxxxxxxxx <mosquitto-dev-bounces@xxxxxxxxxxx> on behalf of mosquitto-dev-request@xxxxxxxxxxx <mosquitto-dev-request@xxxxxxxxxxx>
Sent: Tuesday, April 19, 2016 11:00 AM
To: mosquitto-dev@xxxxxxxxxxx
Subject: mosquitto-dev Digest, Vol 28, Issue 5

Send mosquitto-dev mailing list submissions to
        mosquitto-dev@xxxxxxxxxxx

To subscribe or unsubscribe via the World Wide Web, visit
        https://dev.eclipse.org/mailman/listinfo/mosquitto-dev
or, via email, send a message with subject or body 'help' to
        mosquitto-dev-request@xxxxxxxxxxx

You can reach the person managing the list at
        mosquitto-dev-owner@xxxxxxxxxxx

When replying, please edit your Subject line so it is more specific
than "Re: Contents of mosquitto-dev digest..."


Today's Topics:

   1. Re: Mosquitto c++ lib unexpected disconnect. (Sunderman, Adam)


----------------------------------------------------------------------

Message: 1
Date: Mon, 18 Apr 2016 17:17:00 +0000
From: "Sunderman, Adam" <Adam.Sunderman@xxxxxxxxxxxx>
To: "mosquitto-dev@xxxxxxxxxxx" <mosquitto-dev@xxxxxxxxxxx>
Subject: Re: [mosquitto-dev] Mosquitto c++ lib unexpected disconnect.
Message-ID:
        <a47aaa5e446448d2a1eac3546df9b45a@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Content-Type: text/plain; charset="us-ascii"

Hi Roger,

The on message lead could actually be very relevant. 60 seconds is a lot of time, but you have got me on the lead of a related issue that we have seen that could be causing a list to incorrectly grow over time that the on message callback would be looping through. I will get back in touch with any updated! I can also try to find some time to try with another broker.

I still am curious though, lets say the on message callback somehow does take a ridiculously long time (which I would need to fix of course if that is happening), is there a reason that the connect callback never fires again that I could look into? It seems like it should still be able to fix itself within the mosquitto thread if a timeout did occur. I still find it especially odd that both netstat and rabbit show that the connection is till alive and that I can even successfully publish to the device and see the ack come back on the broker.

Thanks for the prompt response,
Adam
This email is intended solely for the use of the individual to whom it is addressed and may contain confidential and/or privileged material. Any views or opinions presented are solely those of the author and do not necessarily represent those of AGCO. If you are not the intended recipient, be advised that you have received this email in error and that any use, dissemination, forwarding, printing or copying of this email is strictly prohibited. Neither AGCO nor the sender accepts any responsibility for viruses and it is your responsibility to scan and virus check the e-mail and its attachment(s) (if any).


------------------------------

_______________________________________________
mosquitto-dev mailing list
mosquitto-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/mosquitto-dev

End of mosquitto-dev Digest, Vol 28, Issue 5
********************************************
This email is intended solely for the use of the individual to whom it is addressed and may contain confidential and/or privileged material. Any views or opinions presented are solely those of the author and do not necessarily represent those of AGCO. If you are not the intended recipient, be advised that you have received this email in error and that any use, dissemination, forwarding, printing or copying of this email is strictly prohibited. Neither AGCO nor the sender accepts any responsibility for viruses and it is your responsibility to scan and virus check the e-mail and its attachment(s) (if any).