[DO NOT MERGE] Document UseNonPersistentDeliveryMode for IBM MQ transport#8201
Open
[DO NOT MERGE] Document UseNonPersistentDeliveryMode for IBM MQ transport#8201
Conversation
irinascurtu
approved these changes
Apr 23, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This should not be merged until IBMMQ 1.1 is released and more specifically this PR.
When we built IBM MQ transport we were under the assumption the [Express] attribute still existed and unware all of that was removed. We had already added support for the NServiceBus header though, that should enable non-durable messages. We then created PR #80 in IBM MQ repo that adds configuration options to send non-durable messages, but decided not to do yet another release with that PR, since we were already wrapping up the task force and had already done a 1.0.1 release.
This is the PR that adds documentation for when that ability is released in IBM MQ 1.1.