Details
-
Test
-
Status: Closed
-
Major
-
Resolution: Fixed
-
1.15.0
Description
We have ByteBufferConcurrencyTest to test the ByteBuffer reference counting implemented by ByteBufferVendor. But we don't have concurrency tests that focus on the code that interacts with ByteBufferVendor up in NioSslEngine and Connection.
When this ticket is complete we'll have a DUnit test, P2PMessagingConcurrencyDUnitTest, that focuses on that gap via:
- one-way P2P messaging between two peers
- over a shared, ordered connection
- with many concurrent tasks competing for the connection (and its ByteBuffers) on the send side
- with TLS enabled
The test will generate messages of various lengths and will verify that the number of bytes sent matches the number of bytes received and that no exceptions are logged.
The test defines its own subclass of DistributionMessage and sends it via ClusterDistributionManager.putOutgoing(DistributionMessage) so that no higher-level system components are exercised (advisors, regions).
Attachments
Issue Links
- links to