Michael Neumann created ARTEMIS-4304:
----------------------------------------
Summary: Make Consumer Priority an accessible feature of the
Resource Adapter
Key: ARTEMIS-4304
URL: https://issues.apache.org/jira/browse/ARTEMIS-4304
Project: ActiveMQ Artemis
Issue Type: New Feature
Affects Versions: 2.29.0
Reporter: Michael Neumann
As of now, the Consumer Priority Feature, that is present in the JMS Client
Api, is, to my understanding, unusable via the Java EE Resource Adapter. The
information can be specified after a queue Name, just like with the Standard
JMS Client ({{{}"my.destination.name?consumer-priority=50"){}}}, but it is not
evaluated.
The Calls in:
[https://github.com/apache/activemq-artemis/blob/main/artemis-ra/src/main/java/org/apache/activemq/artemis/ra/inflow/ActiveMQMessageHandler.java#L179]
and
[https://github.com/apache/activemq-artemis/blob/main/artemis-ra/src/main/java/org/apache/activemq/artemis/ra/inflow/ActiveMQMessageHandler.java#L158]
lead to the use of the default priority. This could easily be changed with a
call including the priority.
My suggestion would be to also include the priority in the ActivationSpec of
the MDB.
If the feature is deemed useful for the resource adapter, i could also create a
matching Pull Request or patch. The feature would certainly help in my setup.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
