-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
ERROR o.s.i.m.i.MqttPahoMessageDrivenChannelAdapter - Lost connection: Connection lost; retrying... #8798
Comments
First of all we develop here a library of components and really don't experience with target production projects. |
I also encountered the same problem. May I ask if it has been resolved now? Thank you |
We doubled the default values for the 'CompletionTimeout' and 'RecoveryInterval' properties, respectively. I did not find the core problem, but guessed that too many devices were causing the response to time out. |
That's strange. The Would be great if you share your experience after upgrading. Thanks |
Hello, we have encountered a problem, this problem will occur in our production environment, using version 5.5.9, but I can guarantee that the client id is unique, but the connection will be automatically restored soon, no reason has been found, we hope to use your experience to help us, thank your very much!
“ ERROR o.s.i.m.i.MqttPahoMessageDrivenChannelAdapter - Lost connection: Connection lost; retrying...”
The text was updated successfully, but these errors were encountered: