-
Notifications
You must be signed in to change notification settings - Fork 32
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
implement IPersistTimeoutsV2 interface #130
Conversation
@andreasohlund @SzymonPobiega please review |
I am good! |
var t1EnteredTx = new AutoResetEvent(false); | ||
var t2EnteredTx = new AutoResetEvent(false); | ||
|
||
var task1 = Task.Factory.StartNew(() => |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nitpick: Use Task.Run
instead?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
good point. I think we already did that on ravendb, but not on NHibernate
implement IPersistTimeoutsV2 interface
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 Particular/NServiceBus#2885