[GitHub] [james-project] jeantil commented on pull request #1130: JAMES-3805 PulsarMailQueueTest.dequeueShouldBeConcurrent is unstable

[GitBox <gi...@apache.org>]

jeantil commented on PR #1130:
URL: https://github.com/apache/james-project/pull/1130#issuecomment-1216284427

   I had a quick look, my best hypothesis based on the error and the code is that the enqueuing occurs much faster than the dequeuing. This ends up filling the enqueues buffer of 10 elements (not yet configurable) and triggering the backpressure mechanisms. If I understand the documentation correctly, the first item enqueued over buffer capacity will return a pending future, the second one will return a failed future with the error you encounter.
   
   I am not entirely sure what the proper behavior should be... Is there a specific error to throw when the mail queue is unable to accept more messages at this time (rate limit exceeded or a temporary error to invite retrying later ?)
   


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

To unsubscribe, e-mail: notifications-unsubscribe@james.apache.org

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


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@james.apache.org
For additional commands, e-mail: notifications-help@james.apache.org