We could remove the puts as its not doing any tests with put operation; if
its required for establishing initial connection, then do put from client,
clear is not needed.
-Anil.
On Wed, Mar 15, 2017 at 3:54 PM, Darrel Schneider
wrote:
> The problem with this test is that is does register inter
The problem with this test is that is does register interest. The first
client that calls the put method does 2 puts, then a clear, then 2 puts,
then a clear. All of those ops get sent async to the other client. So when
you call the same put method on the second client it can be receiving the
event
I'm looking into a CI test failure
(ClientHealthStatsDUnitTest.testClientHealthStats_SubscriptionEnabled). I
don't see anything wrong with the test so far.
It looks to me like region.getEntry(KEY1) must have either returned a null
RegionEntry or RegionEntry.getValue returned a null immediately aft
