You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by GitBox <gi...@apache.org> on 2018/10/05 04:02:16 UTC

[GitHub] hrsakai opened a new issue #2731: Ws client can't receive any more messages when number of timed-out messages reaches receiverQueueSize

hrsakai opened a new issue #2731: Ws client can't receive any more messages when number of timed-out messages reaches receiverQueueSize
URL: https://github.com/apache/pulsar/issues/2731
 
 
   Ws proxy controls message-delivery to ws client by using `pendingMessages`.
   `pendingMessages` increases when ws proxy sends a message to ws client and It decreases when ws client acks to ws proxy.
   If `pendingMessages` reaches `receiverQueueSize`, ws proxy stops to send a message until ws client acks.
   Even if a message times out(cause by ws client unack), `pendingMessages` doesn't decrease and ws proxy keeps waiting for ack.
   
   #### Expected behavior
   
   When  a message times out, `pendingMessages` decreases.
   
   #### Actual behavior
   
   `pendingMessages` doesn't decrease.
   So ws client can't receive any more messages when timed-out messages reaches `receiverQueueSize`.
   
   #### Steps to reproduce
   
   1. ws client connects to ws proxy url(`ws:<hostname>/ws/consumer/persistent/...?ackTimeoutMillis=1000&receiverQueueSize=2&subscriptionType=Shared`)
   2. producer sends 2 messages.
   3. ws client recieves 2 messages and not ack them.
   4. ws client doesn't receive any more messages until ws client reconnects even if `ackTimeoutMillis`(1000ms) passes.
   
   #### System configuration
   **Pulsar version**: 1.22.1 and 2.2.1
   
   <br>
   <br>
   
   `pendingMessages`
   https://github.com/apache/pulsar/blob/branch-2.2/pulsar-websocket/src/main/java/org/apache/pulsar/websocket/ConsumerHandler.java#L75
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on 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


With regards,
Apache Git Services