-
Notifications
You must be signed in to change notification settings - Fork 47
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
Use default connection check intervals/timeouts in the EFM plugin #274
Conversation
aaron-congo
commented
Nov 22, 2022
•
edited by congoamz
Loading
edited by congoamz
- previously, the interval/timeout values could be set to 0 or Long.MAX_VALUE. This PR changes these values to specified defaults when a user-supplied setting is not available
- also changed various EFM variables to thread-safe variants. These variables are shared between the main thread and the monitor thread
So I'm looking at the title of this and trying to determine how it could be set to MAX_VALUE ? |
There were a couple spots where this.connectionCheckInvervalMillis was being set to the return value of findShortestIntervalMillis in the MonitorImpl file. The original implementation of this function returned MAX_VALUE if there were no contexts in the MonitorImpl class. The fix for this specific problem is in the MonitorImpl changes in this PR |