prevent timeout message loss when not using DTC #2924
Merged
Conversation
This file contains 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
timbussmann
force-pushed
the
hotfix-4.5.7
branch
from
aff4440
to
fb678f6
Compare
timbussmann
force-pushed
the
hotfix-4.5.7
branch
from
fb678f6
to
43e9434
Compare
timbussmann
force-pushed
the
hotfix-4.5.7
branch
from
e5d875c
to
ac28c79
Compare
timbussmann
changed the title
|
|
||
| var config = Configure.With(types) | ||
| //.DefineEndpointName(endpointConfiguration.EndpointName) | ||
| .CustomConfigurationSource(configSource) |
There was a problem hiding this comment.
Why the commented out code?
andreasohlund
added a commit
that referenced
this pull request
Oct 2, 2015
prevent timeout message loss when not using DTC
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Who's affected
You might be affected if you are using one of the following transport configurations:
and you are using timeouts or deferred messages (e.g.
Bus.Defer(...))Symptoms
When experiencing connectivity issues with the transport there's a chance that a due timeout/deferred message is lost. Therefore the message will never arrive.
What to do if you are affected
We highly recommend to update to the latest patch versions of your NServiceBus and optional persistence and transport packages. For more details see issue #2885
Connects to #2885