5 Replies Latest reply on Mar 27, 2014 2:31 AM by Chris Toomey

    Any performance/scalability concerns with scheduled messages?

    Chris Toomey Newbie

      We're considering using scheduled messages with HornetQ for retrying outbound API requests that have failed with a retryable error condition (e.g., target server down or returned a server error).  In a scenario where we have lots of outbound API requests coming in and an extended server error condition, this could result in a large number of scheduled messages.


      What are the performance/scalability issues with scheduled messages, if any, beyond those with regular (unscheduled) messages?


      Also, is it ok to mix scheduled/unscheduled messages in the same queue, or is it recommended to use separate queues for each?