GEODE-1468 client/server messaging can create large objects
After a Message has been sent we invoke clear() on each Part contained by
the Message. This was nulling out the "part" variable of the Part objects
but if one of these "parts" was a HeapDataOutputStream it might hold a
list of large buff
GEODE-1468 client/server messaging can create large objects
After a Message has been sent we invoke clear() on each Part contained by
the Message. This was nulling out the "part" variable of the Part objects
but if one of these "parts" was a HeapDataOutputStream it might hold a
list of large buff
GEODE-1468 client/server messaging can create large objects
After a Message has been sent we invoke clear() on each Part contained by
the Message. This was nulling out the "part" variable of the Part objects
but if one of these "parts" was a HeapDataOutputStream it might hold a
list of large buff
Repository: incubator-geode
Updated Branches:
refs/heads/develop 711fc3518 -> 61ad7e445
GEODE-1468 client/server messaging can create large objects
After a Message has been sent we invoke clear() on each Part contained by
the Message. This was nulling out the "part" variable of the Part objec