You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geode.apache.org by Travis CI <bu...@travis-ci.org> on 2017/07/03 20:18:29 UTC

Broken: apache/geode#3077 (develop - fb4e96b)

Build Update for apache/geode
-------------------------------------

Build: #3077
Status: Broken

Duration: 9 minutes and 25 seconds
Commit: fb4e96b (develop)
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/92f270805a83...fb4e96bfbad9

View the full build log and details: https://travis-ci.org/apache/geode/builds/249764167?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