Skip to content

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.

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))

@cescoffier
Copy link
Contributor

@User-123321123 Could you please have a look at the comments?

@cescoffier
Copy link
Contributor

@ozangunalp @User-123321123 what's the status on this one?

@ozangunalp
Copy link
Collaborator

I didn't have time to test this out. But setting the client priority for each outgoing message didn't seem feasible to me.

In any case going forward, we'd need a test to back it up.

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.

3 participants