We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
As reported in cloudfoundry/cf-java-client#857, the client pooled context does not seem to bridge closeFuture correctly.
The core issue being that https://github.com/reactor/reactor-netty/blob/master/src/main/java/reactor/ipc/netty/channel/PooledClientContextHandler.java#L200 is never true since the channel handler is created before by doPipeline. That means we never attach closeFuture(release(ch)).
The text was updated successfully, but these errors were encountered:
fix #285 - connection close should always be bridged to pool release
a5c512a
f97aaa3
9e33be5
attempt to fix #285 in PooledClientContextHandler
6b698b1
only set the channel closeFuture to release to the pool once we've made sure that we acquired a Channel.
No branches or pull requests
As reported in cloudfoundry/cf-java-client#857, the client pooled context does not seem to bridge closeFuture correctly.
The core issue being that https://github.com/reactor/reactor-netty/blob/master/src/main/java/reactor/ipc/netty/channel/PooledClientContextHandler.java#L200 is never true since the channel handler is created before by doPipeline. That means we never attach closeFuture(release(ch)).
The text was updated successfully, but these errors were encountered: