[GitHub] [geode] jujoramos commented on issue #4978: Fix for regression introduced by GEODE-7565

[GitBox]

jujoramos commented on issue #4978:
URL: https://github.com/apache/geode/pull/4978#issuecomment-617814149


   One additional comment regarding the following waning message:
   
   ```
   [warn 2020/04/18 23:44:22.757 PDT  
tid=0x298] Unable to ping non-member 
rs-FullRegression19040559a2i32xlarge-hydra-client-63(bridgegemfire1_host1_4749:4749):41003
 for client 
identity(rs-FullRegression19040559a2i32xlarge-hydra-client-63(edgegemfire3_host1_1071:1071:loner):50046:5a182991:edgegemfire3_host1_1071,connection=2
   ```
   
   The above is logged by member `bridgegemfire1_host1_4749` in the tests, 
exactly the member to which the `ping` command was sent... this warning is 
logged within the `pingCorrectServer` method which, unless I'm missing 
something, shouldn't be invoked at all if this member is the actual recipient 
for the `ping` message. Maybe `!myID.equals(targetServer)` is not working as 
expected?.



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [geode] jujoramos commented on issue #4978: Fix for regression introduced by GEODE-7565

[GitBox]

jujoramos commented on issue #4978:
URL: https://github.com/apache/geode/pull/4978#issuecomment-617642403


   @bschuchardt @alb3rtobr : I'm still analysing the issue and seeing whether I 
can reproduce it consistently, so far it's proving quite elusive as it only 
fails once or twice in around 100 runs of my test. Will keep you posted.



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org