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/11/20 15:04:55 UTC

[GitHub] jiazhai commented on issue #2731: Ws client can't receive any more messages when number of timed-out messages reaches receiverQueueSize

jiazhai commented on 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#issuecomment-440304897
 
 
   As the [document](https://github.com/apache/pulsar/blob/branch-2.2/pulsar-websocket/src/main/java/org/apache/pulsar/websocket/ConsumerHandler.java#L57) mentioned, In receive, it dispatches further messages after ack.
   
   It seems be working as designed.
   
   ```
   /**
    *
    * WebSocket end-point url handler to handle incoming receive and acknowledge requests.
    * <p>
    * <b>receive:</b> socket-proxy keeps pushing messages to client by writing into session. However, it dispatches N
    * messages at any point and after that on acknowledgement from client it dispatches further messages. <br/>
    * <b>acknowledge:</b> it accepts acknowledgement for a given message from client and send it to broker. and for next
    * action it notifies receive to dispatch further messages to client.
    * </P>
    *
    */
   ```

----------------------------------------------------------------
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