Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
1.4.0
-
None
-
None
Description
In the AbstractRpcSink, when an exception occurs during the process, say a timeout, the connection is destroyed. But when the connection is created again, a new cxnResetExecutor is scheduled. The first one being still scheduled, this may result in many jobs reseting the connection far too often.
I suppose the createConnection should take care of shutting down any existing reset job before creating new ones.