Skip to content
This repository has been archived by the owner on Nov 10, 2020. It is now read-only.

Error peeking next message size: EOF #47

Open
zubairhamed opened this issue Dec 11, 2016 · 2 comments
Open

Error peeking next message size: EOF #47

zubairhamed opened this issue Dec 11, 2016 · 2 comments

Comments

@zubairhamed
Copy link

Running the example code as per the docs throws an error:
Server:

  • 27397 process.go:55/processor] (1/surgemq) Error peeking next message size: EOF

Client:

  • 27425 process.go:55/processor] (1/surgemq) Error peeking next message size: EOF

Env: go version go1.7.3 darwin/amd64

@jianfengye
Copy link

jianfengye commented Jan 11, 2017

got the same error in darwin/amd64

@0xlee
Copy link

0xlee commented Jan 24, 2017

E0124 23:06:59.663901 73278 process.go:55/processor] (1/) Error peeking next message size: EOF
E0124 23:06:59.663895 73278 sendrecv.go:76/receiver] (1/) error reading from connection: read tcp 10.23.205.51:61918->130.211.48.91:1883: i/o timeout

For me the same. It seems to do something with KeepAlive timeout. It happens later if I increase this timeout.

My application didn't subscribe anything, but published only with QoS 0's. If I publish with QoS 1's, the error doesn't occur. (My application publish at least some messages every second)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants