maxfortun commented on PR #949: URL: https://github.com/apache/activemq/pull/949#issuecomment-1374021941
> @maxfortun are you able to share any more details about the use case? I'm pretty sure a standard plugin could support this without needing to modify broker internals or the current scheduler code. @mattrpav we are streaming messages and scheduling some of them for a delayed delivery. We sometimes need to cancel or replace scheduled messages with their latest versions. Currently the only way to interact with the scheduled messages is via a job id. The problem is that the job id is not available until the message is inside the scheduler. The only way to get the job id is to keep polling the broker for its scheduled jobs. Not only this is very inefficient and resource intensive when there are many scheduled messages, but also there is no way to react in event driven fashion to a message that was just scheduled until it was actually dispatched. By sending activity advisory messages with the job Id and group id I can have a pub-sub system that is always in sync with the scheduler and allows me to remove the scheduled jobs by mapping some attributes, like a group id to its job id, and ultimately cancel the job associated with the specific message. I am open to any other means of achieving the same. Although, this feature seems like rather harmless, as it is fully backward compatible and does not get turned on unless explicitly configured. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
