{"push_id":1837600903,"size":1,"distinct_size":1,"ref":"refs/heads/develop","head":"fb4e96bfbad9e66966fd13cd35499bc7f3a020e4","before":"92f270805a83c69da2c1ab469b3206ae6e7c9acf","commits":[{"sha":"fb4e96bfbad9e66966fd13cd35499bc7f3a020e4","author":{"name":"Bruce Schuchardt","email":"74492735cc196c091d33a09270383bbf9db34641@pivotal.io"},"message":"GEODE-3139 remove artifacts from classpath of backward-compatibility tests\n\nreinstating this - passes precheckin\n\nGEODE-3153 Client receives duplicate events during rolling upgrade\n\nAnother problem was found in backward-compatibility testing.  If a\n1.0.0 client was receiving subscription events generated by a 1.0.0\npeer \"feeder\" member and the events were routed through a 1.0.0 server\nthe client might see duplicate events when the server is stopped and\nthe client fails over to a 1.2.0 server holding its redundant\nsubscription queue.  This is especially possible if a large \"ack\"\nperiod is established in the client.\n\nThe problem stems from the EventID deserialization/reserialization of\nthe memberID bytes when sending to a 1.0 client.  It was deserializing\nusing Version.CURRENT, which ignores the UUID bytes in the serialized ID.\nThen it serialized the identifier using the client's version, which\nincludes the UUID bytes but which are zero due to the version used\nin deserialization.","distinct":true,"url":"https://api.github.com/repos/apache/geode/commits/fb4e96bfbad9e66966fd13cd35499bc7f3a020e4"}]}
{"actor":{"display_login":"asfgit"}}