Build Update for apache/geode ------------------------------------- Build: #3078 Status: Broken
Duration: 5 minutes and 32 seconds Commit: 30e2eb2 (release/1.2.0) Author: Bruce Schuchardt Message: GEODE-3139 remove artifacts from classpath of backward-compatibility tests reinstating this - passes precheckin GEODE-3153 Client receives duplicate events during rolling upgrade Another problem was found in backward-compatibility testing. If a 1.0.0 client was receiving subscription events generated by a 1.0.0 peer "feeder" member and the events were routed through a 1.0.0 server the client might see duplicate events when the server is stopped and the client fails over to a 1.2.0 server holding its redundant subscription queue. This is especially possible if a large "ack" period is established in the client. The problem stems from the EventID deserialization/reserialization of the memberID bytes when sending to a 1.0 client. It was deserializing using Version.CURRENT, which ignores the UUID bytes in the serialized ID. Then it serialized the identifier using the client's version, which includes the UUID bytes but which are zero due to the version used in deserialization. View the changeset: https://github.com/apache/geode/compare/9f55eb125514...30e2eb2080af View the full build log and details: https://travis-ci.org/apache/geode/builds/249764972?utm_source=email&utm_medium=notification -- You can configure recipients for build notifications in your .travis.yml file. See https://docs.travis-ci.com/user/notifications
