![]() In this way you could separate the scheduling from the work distribution. Something like the quartz scheduler might be a good solution here because you could schedule all the tasks with it, and the scheduled task could send a message to a queue which is being monitored by your distributed workers. There is not automated, repeated delivery of the same message. Once that message is delivered and consumed it's gone which means you'll need to send another scheduled message. You can use scheduled delivery but that only applies for a single message. The current goal in the ActiveMQ community is that Artemis will become the 6.x version of ActiveMQ. It is based on a newer, fundamentally non-blocking design and it supports all of the protocols and much of the same functionality as ActiveMQ 5.x. However, it is separate from the "classic" ActiveMQ broker code-base. ![]() Apache ActiveMQ Artemis is a message broker which is part of the ActiveMQ project.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |