You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geode.apache.org by GitBox <gi...@apache.org> on 2020/04/20 13:45:54 UTC

[GitHub] [geode] jujoramos opened a new pull request #4974: Revert "GEODE-7565: Allow gateway receivers with same host and port

jujoramos opened a new pull request #4974:
URL: https://github.com/apache/geode/pull/4974


   This reverts commit dd23ee8200cba67cea82e57e2e4ccedcdf9e8266.
   
   Intermittent errors were observed while executing some internal tests and commit dd23ee8200cba67cea82e57e2e4ccedcdf9e8266 was determined to be responsible. As of yet, no local reproduction of the issue is available, but work is ongoing to provide a test that can be used to debug the issue.
   The below stack trace is an example of the issues we're seeing:
   
   ```
   [error 2020/04/18 23:44:22.758 PDT <poolTimer-edgeDescript-31> tid=0x165] Unexpected error in pool task <or...@3483b110>
   org.apache.geode.InternalGemFireError: Unexpected message type PING
   	at org.apache.geode.cache.client.internal.AbstractOp.processAck(AbstractOp.java:264)
   	at org.apache.geode.cache.client.internal.PingOp$PingOpImpl.processResponse(PingOp.java:82)
   	at org.apache.geode.cache.client.internal.AbstractOp.processResponse(AbstractOp.java:222)
   	at org.apache.geode.cache.client.internal.AbstractOp.attemptReadResponse(AbstractOp.java:207)
   	at org.apache.geode.cache.client.internal.AbstractOp.attempt(AbstractOp.java:382)
   	at org.apache.geode.cache.client.internal.ConnectionImpl.execute(ConnectionImpl.java:268)
   	at org.apache.geode.cache.client.internal.pooling.PooledConnection.execute(PooledConnection.java:352)
   	at org.apache.geode.cache.client.internal.OpExecutorImpl.executeWithPossibleReAuthentication(OpExecutorImpl.java:753)
   	at org.apache.geode.cache.client.internal.OpExecutorImpl.executeOnServer(OpExecutorImpl.java:332)
   	at org.apache.geode.cache.client.internal.OpExecutorImpl.executeOn(OpExecutorImpl.java:303)
   	at org.apache.geode.cache.client.internal.PoolImpl.executeOn(PoolImpl.java:839)
   	at org.apache.geode.cache.client.internal.PingOp.execute(PingOp.java:38)
   	at org.apache.geode.cache.client.internal.LiveServerPinger$PingTask.run2(LiveServerPinger.java:90)
   	at org.apache.geode.cache.client.internal.PoolImpl$PoolTask.run(PoolImpl.java:1329)
   	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
   	at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
   	at org.apache.geode.internal.ScheduledThreadPoolExecutorWithKeepAlive$DelegatingScheduledFuture.run(ScheduledThreadPoolExecutorWithKeepAlive.java:276)
   	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
   	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
   	at java.lang.Thread.run(Thread.java:748)
   ```
   
   Thank you for submitting a contribution to Apache Geode.
   
   In order to streamline the review of the contribution we ask you
   to ensure the following steps have been taken:
   
   ### For all changes:
   - [ ] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message?
   
   - [ ] Has your PR been rebased against the latest commit within the target branch (typically `develop`)?
   
   - [ ] Is your initial contribution a single, squashed commit?
   
   - [ ] Does `gradlew build` run cleanly?
   
   - [ ] Have you written or updated unit tests to verify your changes?
   
   - [ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under [ASF 2.0](http://www.apache.org/legal/resolved.html#category-a)?
   
   ### Note:
   Please ensure that once the PR is submitted, check Concourse for build issues and
   submit an update to your PR as soon as possible. If you need help, please send an
   email to dev@geode.apache.org.
   


----------------------------------------------------------------
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:
users@infra.apache.org



[GitHub] [geode] jujoramos edited a comment on issue #4974: Revert "GEODE-7565: Allow gateway receivers with same host and port

Posted by GitBox <gi...@apache.org>.
jujoramos edited a comment on issue #4974:
URL: https://github.com/apache/geode/pull/4974#issuecomment-616565367


   @alb3rtobr: I'm just tagging you as you are the author of the original commit so you're aware of the revert request, I'll try to reproduce the issue using a `DistributedTest` and will share it with you afterwards (let's use [GEODE-8004](https://issues.apache.org/jira/browse/GEODE-8004) for communication purposes).
   


----------------------------------------------------------------
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:
users@infra.apache.org



[GitHub] [geode] jujoramos commented on issue #4974: Revert "GEODE-7565: Allow gateway receivers with same host and port

Posted by GitBox <gi...@apache.org>.
jujoramos commented on issue #4974:
URL: https://github.com/apache/geode/pull/4974#issuecomment-616565367


   @alb3rtobr 


----------------------------------------------------------------
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:
users@infra.apache.org



[GitHub] [geode] jujoramos edited a comment on issue #4974: Revert "GEODE-7565: Allow gateway receivers with same host and port

Posted by GitBox <gi...@apache.org>.
jujoramos edited a comment on issue #4974:
URL: https://github.com/apache/geode/pull/4974#issuecomment-616565367


   @alb3rtobr: I'm just tagging you as you are the author of the original commit so you're aware of the revert request, I'll try to reproduce the issue using a `DistributedTest` and will share it with you afterwards.
   


----------------------------------------------------------------
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:
users@infra.apache.org



[GitHub] [geode] jujoramos edited a comment on issue #4974: Revert "GEODE-7565: Allow gateway receivers with same host and port

Posted by GitBox <gi...@apache.org>.
jujoramos edited a comment on issue #4974:
URL: https://github.com/apache/geode/pull/4974#issuecomment-616565367


   @alb3rtobr: I'm just tagging you as you are the author of the original commit so you're aware of the revert request, I'll try to reproduce the issue using a `DistributedTest` and will share it with you afterwards (let's use [GEODE-8004](https://issues.apache.org/jira/browse/) for communication purposes).
   


----------------------------------------------------------------
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:
users@infra.apache.org



[GitHub] [geode] bschuchardt commented on issue #4974: Revert "GEODE-7565: Allow gateway receivers with same host and port

Posted by GitBox <gi...@apache.org>.
bschuchardt commented on issue #4974:
URL: https://github.com/apache/geode/pull/4974#issuecomment-616668765


   The problem might be in changes to Ping.java.  It may send an error response back to the client with MessageType.PING, which maybe the client isn't equipped to deal with.


----------------------------------------------------------------
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:
users@infra.apache.org