[cleanup][proxy] ProxyConnection should not call super.exceptionCaught

[michaeljmarshall]

Motivation

While debugging an issue, I noticed that we call super.exceptionCaught(ctx, cause); in the ProxyConnection class. This leads to the following log line:

An exceptionCaught() event was fired, and it reached at the tail of the pipeline. It usually means the last handler in the pipeline did not handle the exception. io.netty.channel.unix.Errors$NativeIoException: recvAddress(..) failed: Connection reset by peer

Because we always handle exceptions, there is no need to forward them to the next handler.

Modifications

• Remove a single method call

Verifying this change

This is a trivial change. Note that we do not call the super method in any other handler implementations in the project.

Documentation

• doc-not-needed

Matching PR in forked repository

PR in forked repository: skipping PR for this trivial change

[lhotari]

I guess the only problem that the method call caused is the extra log line?

[lhotari]

/pulsarbot rerun-failure-checks

[michaeljmarshall]

I guess the only problem that the method call caused is the extra log line?

Correct. The only problem was an extra log line. It is only a cosmetic issue, as far as I can tell.

[michaeljmarshall]

/pulsarbot rerun-failure-checks