Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

client terminates a connection shortly after publishing a message #5

Open
traut opened this issue Jan 12, 2018 · 0 comments
Open

client terminates a connection shortly after publishing a message #5

traut opened this issue Jan 12, 2018 · 0 comments

Comments

@traut
Copy link

traut commented Jan 12, 2018

I'm seeing strange behaviour: shortly after publishing a message, client dies with connection timed out (waiting for :PINGRESP).
My code is very similar to the example provided in READE.md, with one difference -- I call mqtt:publish from a thread (via bordeaux-threads). If I setup the code to just listen for a connection (in an event loop), I can consume messages and in mosquitto log I see messages like:

1515795903: Received PINGREQ from cl-mqtt
1515795903: Sending PINGRESP to cl-mqtt

But shortly after I publish anything, I get:

connection timed out (waiting for :PINGRESP)

and server logs:

1515795988: Socket error on client cl-mqtt, disconnecting.

I counted PINGREQ/PINGRESP in the server's log file and I do not see any un-answered requests. It seems cl-mqtt never sends PINGREQ but expectes PINGRESP. Any ideas?

my setup:

  • cl-mqtt, master branch
  • mosquitto mqtt server
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant