Fix the handler instance is expired when the connection is established #323
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.
Motivation
We observed some logs that showed the handler instance is expired when the connection is established after a reconnection:
pulsar-client-cpp/lib/HandlerBase.cc
Line 92 in b35ae1a
Modifications
Pass a
shared_ptrinstead of aweak_ptrinHandlerBase::grabCnxto ensure theconnectionOpenedorconnectionFailedcallback is called ifClientImpl::getConnectionis called. We only need to pass aweak_ptrinscheduleReconnectionto skip the reconnection if the handler is expired.