[SENTRY-1928] HMSFollower should close HMS connections when an error to HMS occurs

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 2.0.0
• Fix Version/s: 2.0.0
• Component/s: Sentry
• Assignee: Sergio Peña
• Reporter: Sergio Peña
• Created: 06/Sep/17 21:57
• Updated: 07/Sep/17 03:39
• Resolved: 07/Sep/17 03:39

Description

Sometimes the HMSFollower fails getting notifications from a HMS-HA environment because of SocketTimeoutExceptions. When this exception happens, the HMSFollower does not close such connection and it attempts to get notifications from the same HMS service causing a deadlock between HMS sync notifications listener and Sentry.

We should close the current HMS connections and re-connect to another HMS service if this SocketTimeoutException happens or any other error with the HMS happens.

Issue Links

• links to: Review Board