Skip to content
New issue

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

[Transactions] Prevent NPE in case of closeAsync() without a successful execution of startAsync() #10948

Merged
merged 1 commit into from
Jun 17, 2021

Conversation

eolivelli
Copy link
Contributor

Fixes #10947

Motivation

If the initialisation of TransactionCoordinatorClientImpl is not completed calling closeAsync will result in a NPE.

Modifications

Add a null check

Verifying this change

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

@codelipenghui codelipenghui merged commit 3fd1bfd into apache:master Jun 17, 2021
yangl pushed a commit to yangl/pulsar that referenced this pull request Jun 23, 2021
…ul execution of startAsync() (apache#10948)

Fixes apache#10947
### Motivation

If the initialisation of TransactionCoordinatorClientImpl is not completed calling closeAsync will result in a NPE.
@codelipenghui codelipenghui added the cherry-picked/branch-2.8 Archived: 2.8 is end of life label Jun 25, 2021
codelipenghui pushed a commit that referenced this pull request Jun 25, 2021
…ul execution of startAsync() (#10948)

Fixes #10947
### Motivation

If the initialisation of TransactionCoordinatorClientImpl is not completed calling closeAsync will result in a NPE.

(cherry picked from commit 3fd1bfd)
bharanic-dev pushed a commit to bharanic-dev/pulsar that referenced this pull request Mar 18, 2022
…ul execution of startAsync() (apache#10948)

Fixes apache#10947
### Motivation

If the initialisation of TransactionCoordinatorClientImpl is not completed calling closeAsync will result in a NPE.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants