[NIFI-4742] CaptureChangeMySQL memory/thread leak when enrichment connection cannot be made

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.5.0
• Component/s: Extensions
• Assignee: Matt Burgess
• Reporter: Matt Burgess
• Created: 05/Jan/18 20:06
• Updated: 05/Jan/18 21:02
• Resolved: 05/Jan/18 21:02

Description

CaptureChangeMySQL, in addition to making a connection to read the binary logs, will try to make a JDBC connection to the database in order to enrich the CDC events with information not in the binary logs themselves, such as column names/types.

However if an error occurs during set up of the JDBC connection (such as a missing driver, bad class name, etc.), the binary log connection (including keepalive thread) is not being cleaned up, and upon retry will create new threads, etc.

If the JDBC connection cannot be set up successfully, all resources should be released and/or cleaned up for a fresh retry.

Issue Links

• links to: GitHub Pull Request #2379