|Re: [paho-dev] Paho C: MIPS CPU usage|
on the failing trace, without the sleep, MQTTClient_cycle is returning -1 (error) which is not the case for the working trace. It seems you probably spotted that from the location of the sleep you added. It looks like getReadySocket is returning too quickly, when the socket is not actually ready. If you could get an strace of network calls in the failing scenario, that might help narrow it down.
How many client objects are there? Are they all using TLS? Exactly the same application works on a non MIPS architecture Linux?
On 04/01/2016 07:53 AM, Milan Tucic wrote:
-- Ian Craggs icraggs@xxxxxxxxxx IBM United Kingdom Paho Project Lead; Committer on Mosquitto
Back to the top