|Re: [mosquitto-dev] Mosquitto Bug with Ping|
Thank you Roger,now i resolve the problem not sending a ping but sending a subscribtion to the broker from GW003cmd and in these way it works...
i'll check if the ping packet that i send is correct! Il 2015-02-23 22:48 Roger Light ha scritto:
Hi there, I've run many successful tests like this with a single host having multiple connections to a remote broker. I'm afraid I think that it is much more likely that there is a bug somewhere in the software stack on your microcontroller. Is there anything else that you can test? Regards, Roger On Mon, Feb 23, 2015 at 11:12 AM, <massarelli@xxxxxxxxx> wrote:Hi, I have these situation and I think that probably there is a bug in mosquitto: I have two socket from a microcontroller that connect to the broker: -the first socket is binded with port 1883 in the microcontroller and connect to the port 1883 with the broker with clientID 'GW003'-the second is binded with port 1800 in the microcontroller and connectto the port 1883 with the broker with clientID 'GW003cmd' I use the first socket only for publish. And the second only for subscribe. Each second i publish a message from GW003 and i send a ping from GW003cmd waiting for some message to arrive.However i see that when I ping mosquitto see that i'm pinging from GW003and not GW003cmd and so after some time it disconnect GW003cmd. I verified that if i subscribe to some topic mosquitto con distinguish beetween GW003 and GW003cmd. _______________________________________________ mosquitto-dev mailing list mosquitto-dev@xxxxxxxxxxxTo change your delivery options, retrieve your password, or unsubscribe fromthis list, visit https://dev.eclipse.org/mailman/listinfo/mosquitto-dev_______________________________________________ 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
Back to the top