Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Added dynamic priority support for jms similar to amqp #2915

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

User-123321123
Copy link

Added priority to OutgoingJmsMessageMetadata, which allows setting the priority before sending the message. The ampq connector implementation provides a similar feature.

@@ -156,6 +157,9 @@ private Uni<? extends Message<?>> send(JmsResourceHolder<JMSProducer> resourceHo
if (type != null) {
outgoing.setJMSType(type);
}
if (priority != null) {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shouldn't this set the priority on the outgoing message?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That was my first thought too, but using outgoing.setJMSPriority(priority); is not working. Could this be a mapping problem with the jakarta.jms.Message outgoing?

Setting it directly on the sender did work for me (resourceHolder.getClient().setPriority(priority))

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants