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

ERROR o.s.i.m.i.MqttPahoMessageDrivenChannelAdapter - Lost connection: Connection lost; retrying... #8798

Open
cmm1 opened this issue Nov 27, 2023 · 4 comments
Labels
status: waiting-for-reporter Needs a feedback from the reporter type: bug

Comments

@cmm1
Copy link

cmm1 commented Nov 27, 2023

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...”

@cmm1 cmm1 added status: waiting-for-triage The issue need to be evaluated and its future decided type: bug labels Nov 27, 2023
@artembilan
Copy link
Member

First of all we develop here a library of components and really don't experience with target production projects.
Secondly, it would be great to have some simple project from you to be able to reproduce on our side.
And third: 5.5.x is out of Open Source support since last week, so it would be great if you can upgrade your solution to the latest supported version of Spring Integration and let us know how it behaves.

@artembilan artembilan added status: waiting-for-reporter Needs a feedback from the reporter and removed status: waiting-for-triage The issue need to be evaluated and its future decided labels Nov 27, 2023
@yulin98
Copy link

yulin98 commented Apr 12, 2024

I also encountered the same problem. May I ask if it has been resolved now? Thank you

@cmm1
Copy link
Author

cmm1 commented Apr 12, 2024

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.

@artembilan
Copy link
Member

That's strange. The completionTimeout is already 30 seconds by default...
The reconnect must be handled by the client.
Apparently both of you are using very old, out of support, Spring Integration version.

Would be great if you share your experience after upgrading.

Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: waiting-for-reporter Needs a feedback from the reporter type: bug
Projects
None yet
Development

No branches or pull requests

3 participants