You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm running on a Debian Bullseye container. The container has access to a rfcomm device on the host and I'm using a listener to detect if the connection is closed to try and reconnect the device. This works well up to a point when the program gets several disconnection events in a row and then freezes while trying to reconnect.
The reconnection mechanism just calls closePort waits a few seconds and tries to call openPort again
Running jconsole remotely shows that there's a live thread running waitForEvent so I assume the listener it's still registered in the SerialPort instance.
Depending on how you are doing your reconnection logic, I can see how it's possible for the waitForEvent loop to persist. I just made some updates to ensure that the loop exits if a disconnect event is detected. If you have the ability to test your code with the most recent SNAPSHOT version, that would be very helpful. Thanks!
Activity
hedgecrw commentedon Nov 4, 2025
Depending on how you are doing your reconnection logic, I can see how it's possible for the
waitForEventloop to persist. I just made some updates to ensure that the loop exits if a disconnect event is detected. If you have the ability to test your code with the most recent SNAPSHOT version, that would be very helpful. Thanks!yorodm commentedon Nov 15, 2025
Hi @hedgecrw , sadly I'm not longer involved with the project in question and I don't have access to the codebase.