Uploaded image for project: 'Apache RocketMQ'
  1. Apache RocketMQ
  2. ROCKETMQ-324

Expose an interface for client to specify the async call back executor

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 4.0.0-incubating, 4.1.0-incubating
    • Fix Version/s: 4.2.0
    • Component/s: rocketmq-client
    • Labels:
      None

      Description

      Currently, the async call back will be executed in a public executor which is mainly used in CHECK_TRANSACTION_STATE, NOTIFY_CONSUMER_IDS_CHANGED, CONSUME_MESSAGE_DIRECTLY, etc. More details please refer to MQClientAPIImpl.

      Should expose an interface for client to specify the independent call back executor.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Yukon yukon
                Reporter:
                Yukon yukon
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: