Bill opened a new pull request #5698:
URL: https://github.com/apache/geode/pull/5698


   * GEODE-8020: buffer management problems
   
   This fixes some buffer handling in MsgStreamerList and alters
   MstStreamer to avoid creating MsgStreamerList and VersionedMsgStreamers
   during normal, non-upgrade, operations.
   
   It also changes NioSslEngine to use synchronization in more places,
   notably the close() method, which was possibly allowing multiple threads to
   change the state of the engine.
   
   * revert unnecessary change to ClusterCommunicationsDUnitTest
   
   * fixing another null version check
   
   * renamed new BufferPool property
   
   * restore logging of ssl exceptions
   
   (cherry picked from commit 7375c591f25bbba413237aed1f56f8a9f70075df)
   
   Thank you for submitting a contribution to Apache Geode.
   
   In order to streamline the review of the contribution we ask you
   to ensure the following steps have been taken:
   
   ### For all changes:
   - [ ] Is there a JIRA ticket associated with this PR? Is it referenced in 
the commit message?
   
   - [ ] Has your PR been rebased against the latest commit within the target 
branch (typically `develop`)?
   
   - [ ] Is your initial contribution a single, squashed commit?
   
   - [ ] Does `gradlew build` run cleanly?
   
   - [ ] Have you written or updated unit tests to verify your changes?
   
   - [ ] If adding new dependencies to the code, are these dependencies 
licensed in a way that is compatible for inclusion under [ASF 
2.0](http://www.apache.org/legal/resolved.html#category-a)?
   
   ### Note:
   Please ensure that once the PR is submitted, check Concourse for build 
issues and
   submit an update to your PR as soon as possible. If you need help, please 
send an
   email to [email protected].
   


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to