Fix crash when removing connection from the pool #347
Merged
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 #346
Motivation
#336 changes the key of the
ClientConnection
inConnectionPool
, while inClientConnection::close
, it still passes the old key (logical address) toConnectionPool::remove
, which results in the connection could never be removed and destroyed until being deleted as a stale connection.What's worse, if the key does not exist, the iterator returned by
std::map::find
will still be dereferenced, which might cause crash in some platforms. Seepulsar-client-cpp/lib/ConnectionPool.cc
Lines 122 to 123 in 8d32fd2
Modifications
ConnectionPool::remove
.ClientConnection
and pass the correct key toConnectionPool::remove
inClientConnection::close
ClientTest.testConnectionClose
to verifyClientConnection::close
can remove itself from the pool and the connection will be destroyed eventually.