[
https://issues.apache.org/jira/browse/NIFI-4742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16313871#comment-16313871
]
ASF subversion and git services commented on NIFI-4742:
-------------------------------------------------------
Commit e43f07e31db34fbdaebc2a57ab3548cfaf4322da in nifi's branch
refs/heads/master from [~ca9mbu]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=e43f07e ]
NIFI-4742: Clean up CaptureChangeMySQL connection resources on connect failure.
This closes #2379
> CaptureChangeMySQL memory/thread leak when enrichment connection cannot be
> made
> -------------------------------------------------------------------------------
>
> Key: NIFI-4742
> URL: https://issues.apache.org/jira/browse/NIFI-4742
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Reporter: Matt Burgess
> Assignee: Matt Burgess
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
