Skip to content

Fixed|SimpleChannelPool.close() should only return after complete.#7927

Merged
normanmaurer merged 1 commit into4.1from
pool_close
May 21, 2018
Merged

Fixed|SimpleChannelPool.close() should only return after complete.#7927
normanmaurer merged 1 commit into4.1from
pool_close

Conversation

@normanmaurer
Copy link
Copy Markdown
Member

Motivation:

We need to ensure we only return from close() after all work is done as otherwise we may close the EventExecutor before we dispatched everything.

Modifications:

Correctly wait on operations to complete before return.

Result:

Fixes #7901.

Motivation:

We need to ensure we only return from close() after all work is done as otherwise we may close the EventExecutor before we dispatched everything.

Modifications:

Correctly wait on operations to complete before return.

Result:

Fixes #7901.
@normanmaurer
Copy link
Copy Markdown
Member Author

@trustin ping

@normanmaurer normanmaurer self-assigned this May 21, 2018
@normanmaurer normanmaurer added this to the 4.1.26.Final milestone May 21, 2018
@normanmaurer normanmaurer merged commit 583fc27 into 4.1 May 21, 2018
@normanmaurer normanmaurer deleted the pool_close branch May 21, 2018 17:22
dagnir added a commit to dagnir/aws-sdk-java-v2 that referenced this pull request Mar 12, 2019
Backport changes from netty/netty#7927, which fixes the
close method so that the call to the delegateChannelPool#close is done on a
separate thread that isn't the executor.
dagnir added a commit to aws/aws-sdk-java-v2 that referenced this pull request Mar 13, 2019
Backport changes from netty/netty#7927, which fixes the
close method so that the call to the delegateChannelPool#close is done on a
separate thread that isn't the executor.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Netty Client concurrent issue when close FixedChannelPool

2 participants