michaelandrepearce edited a comment on issue #2548: ARTEMIS-2118 Enhanced Message Groups Support URL: https://github.com/apache/activemq-artemis/pull/2548#issuecomment-463091333 @billpoole-mi No there wont be any special message. The intent here is for apps where you want evenly load balanced groups but where apps can handle a slight change in which groups they are handling with out special handling, e.g. this is very usefull where a stateless app that simply needs to process and enrich data, and produces onwards. Any data relating to the group can be loaded lazily, and lazily expire out. RE: JMSXGroupLastForConsumer its not possible to retro-acitvely add a header, because consumers can be added at anypoint, and at that point the group may not have a message to dispatch onwards it would not be possible so it would not be possible to add. Also note for AMQP messages we cannot alter by spec. RE: consumer releasing a message it maybe already processing, again no, any already dispatched messages wont be affected, also there is no scope in JMS api to support such release semantic. This said if you have the need, you can though listen for notification CONSUMER_ADDED on notifications address, and as such could then if you know that queue is using that feature, could know rebalance will occur. Obviously if you find a way to add those further enhancements you're always welcome to contribute such features yourself.
---------------------------------------------------------------- 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: us...@infra.apache.org With regards, Apache Git Services
