JMS architectural issue?

Hello,

In the application I'm working on, I have a lengthy process (DNA analysis). Users can send requests, and I think about the order of requests in the JMS queue, and then process the requests in the queue accordingly. The result is then emailed to a specific user.

However, the administrator must be able to change the order / priority of requests. I am wondering if it is possible to change the order of the JMS queue. What technology can I use? Can I go with ActiveMQ for this?

PS: This DNA analysis process is a hungry resource process accessed through JNI. Only one (or limited) process should start immediately.

+3
source share
2 answers

If your processes are long (and you do not have other requirements that correspond to the messaging domain), you can simply query the database table for new tasks (sorted by priority). Spring JDBC abstractions should be enough to get you started. If you use the Oracle DBMS, you can replace the survey with a subscription using triggers and AQ - this can also be done in simple SQL.

Without other requirements, you do not need ORM or JMS.

+1
source

Here are a few ideas that come to mind:

  • AFAIK, the body of the JMS message is immutable, so if you want to change the contents of the body, you will have to use and resubmit the modified version of the JMS message to the queue.

  • - - JMS-, (-), .

  • JMS- Quartz Quartz ( JMS?).

+3

Source: https://habr.com/ru/post/1718772/


All Articles