Fix proxy conn multi broker

[Technoboy-]

Motivation

When client uses the same connection to subscribe many topics, the mop proxy will create multi connections to the target broker. If some of the channel(proxy to broker) has no msg, the channel will be closed due to inactive event. In this case, the mop proxy could close the only one connection. and cause the client to be in a wrong behavior.

TestProxyConnectMultiBroker could reproduce this issue.

Modifications

Describe the modifications you've done.

Verifying this change

• Make sure that the change passes the CI checks.

(Please pick either of the following options)

This change is a trivial rework / code cleanup without any test coverage.

(or)

This change is already covered by existing tests, such as (please describe tests).

(or)

This change added tests and can be verified as follows:

(example:)

• Added integration tests for end-to-end deployment with large payloads (10MB)
• Extended integration test for recovery after broker failure

Documentation

Check the box below.

Need to update docs?

• doc-required

  (If you need help on updating docs, create a doc issue)

• no-need-doc

  (Please explain why)

• doc

  (If this PR contains doc changes)

[github-actions]

@Technoboy-:Thanks for your contribution. For this PR, do we need to update docs?
(The PR template contains info about doc, which helps others know more about the changes. Can you provide doc-related info in this and future PR descriptions? Thanks)

[github-actions]

@Technoboy-:Thanks for your contribution. For this PR, do we need to update docs?
(The PR template contains info about doc, which helps others know more about the changes. Can you provide doc-related info in this and future PR descriptions? Thanks)

[github-actions]

@Technoboy-:Thanks for your contribution. For this PR, do we need to update docs?
(The PR template contains info about doc, which helps others know more about the changes. Can you provide doc-related info in this and future PR descriptions? Thanks)

[caihualin]

adapterChannel.registerClosureListener(future -> {
topicBrokers.values().remove(adapterChannel);
if (topicBrokers.values().size() <= 1) {
if (log.isDebugEnabled()) {
log.debug("Adapter channel inactive, close related connection {}", connection);
}
connection.getChannel().close();
} else {
if (log.isDebugEnabled()) {
log.debug("connection {} has more than one AdapterChannel", connection);
}
}
});
It seems that there is a memory leak here.