mqtt-users team mailing list archive

["Nicholas O'Leary" <nick.oleary@xxxxxxxxx>]

Thanks for the link - hadn't spotted the bug report.

You'll be glad to hear I have reproduced and identified the issue in
my Arduino MQTT Client library.

The code didn't always check there was data available to read before
trying to read from the network. This has not been a problem when
running against the brokers I test against. However, for some reason,
when reading a packet from mosquitto, it is a problem.

Have pushed the fix out as v1.3 - http://knolleary.net/arduino-client-for-mqtt/

Cheers,
Nick


On 27 February 2010 19:39, Oliver Smith <chemicaloli@xxxxxxxxx> wrote:
> I've made an additional note on the bug report which made it work
> better (but not fully) if you've not seen already.
>
> https://bugs.launchpad.net/mosquitto/+bug/528663
>
> On 27 February 2010 15:26, Nicholas O'Leary <nick.oleary@xxxxxxxxx> wrote:
>> Hi,
>>
>> Oliver pinged me last week about this, but I was away on holiday so missed it.
>>
>> I have just tried it and I can confirm the arduino client is unable to
>> connect to mosquitto.
>>
>> The mosquitto log shows:
>>   New client connected from 172.16.0.57.
>>   Socket read error on client arduino, disconnecting.
>>
>>
>> With the current version of the ethernet library, each byte of a
>> message is sent as a separate TCP packet. This is obviously quite
>> inefficient and there was some discussion about improving the outbound
>> buffering of the library. I have not checked recently to see where
>> that has got to.
>>
>> This could be a potential difference in behaviour at the socket level
>> to other clients that mosquitto isn't handling.
>>
>>
>> Cheers,
>> Nick
>>
>> http://knolleary.net
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~mqtt-users
>> Post to     : mqtt-users@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~mqtt-users
>> More help   : https://help.launchpad.net/ListHelp
>>
>