Uploaded image for project: 'ActiveMQ'
  1. ActiveMQ
  2. AMQ-3985

ActiveMQConnection temp advisory consumer should use asyncDispatch - can cause deadlock with slow consumers

    XMLWordPrintableJSON

    Details

      Description

      A slow or blocked connection with the default temp advisory consumer can cause operations that create advisories to block b/c the dispatch is sync to that advisory consumer. If the block occurs after the prefetch is filled the broker stores pending messages and the problem is avoided, but if the block occurs before the prefetch is reached, the dispatch is attempted in the calling thread, which blocks the originating operation. not good.
      The solution is to always request async dispatch for the temp advisory consumer in a client connection.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                gtully Gary Tully
                Reporter:
                gtully Gary Tully
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: