Thanks for your answer Dan! We have checked that setting "0.0.0.0" in
DirectChannel and in GMSHealthMonitor seems to solve our problem. I created PR
to check if using "0.0.0.0" could have an impact and all public test cases
seems to work fine in that case (https://github.com/apache/geode/pull/59
Hi Geode devs,
I have just published the following RFC in the Geode wiki: "Add option to allow
newer Geode clients to connect to older Geode servers"
https://cwiki.apache.org/confluence/display/GEODE/Add+option+to+allow+newer+Geode+clients+to+connect+to+older+Geode+servers
Could you please prov
It sounds like you intend to test which versions are compatible with each other
and maintain a list the client can use to reject the setting of force-version
when set to an incompatible version. If that’s the case, why not just have the
handshake look at that list and automatically connect with
Thanks for your comments, Patrick.
Do you mean have the client always use in the handshake the oldest server
version it is compatible with?
Sounds like a reasonable simplification. In that case, I would use a flag to
activate this behavior so that the current behavior (the client sends the
cur
