GH-9430: Fix CachingClientCF for collaborating channel adapters #9431
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes: #9430
When
CachingClientConnectionFactory
is used in combination ofTcp.outboundAdapter()
&Tcp.inboundAdapter()
, the connection is not released back to the cache becauseCachingClientConnectionFactory
does not store created connections into itsconnections
property. So, whenTcpReceivingChannelAdapter
callsthis.clientConnectionFactory.closeConnection(connectionId);
it returned immediately because there is nothing to remove from thethis.connections
protected removeConnection()
in theAbstractConnectionFactory
and override it in theCachingClientConnectionFactory
with delegation to thethis.targetConnectionFactory
IpIntegrationTests.allRepliesAreReceivedViaLimitedCachingConnectionFactory()
test and ensure that all 27 letters from English alphabet are sent to the server and received in uppercase while size of theCachingClientConnectionFactory
is only10
Auto-cherry-pick to
6.3.x
&6.2.x