Connection leak possibility on some plugin tasks #1227
Labels
area/backend
Needs backend code changes
bug
Something isn't working
kind/cooldown
Great candidate for the cooldown period
Expected Behavior
Using try/catch on connection instantiation eveywhere to avoid possible connection leak
Actual Behaviour
Plugins that open connection usually don't do it in a reliant manner using try/catch/finally risking connection leak in case of exception.
An example can be found in the Kafka
Consume
task.We need to check all connection-based plugins for such issues
The text was updated successfully, but these errors were encountered: