You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The TimeSent header seems to be overwritten with the time the timeout manager dispatched the message to the transport which results in the real timesent value to be lost.
This results in aged timeout manager entries that can be many years old to be sent as now.
The
TimeSent
header seems to be overwritten with the time the timeout manager dispatched the message to the transport which results in the real timesent value to be lost.This results in aged timeout manager entries that can be many years old to be sent as now.
Tested with:
Core:
This configuration cannot be tested with a later version due to the timeout manager not being used.
With v7 only MSMQ would currently be affected but with v6 most transports can be affected due to timeout manager its backwards compatibility.
Data
RavenDB Timeout document:
Headers of received timeout:
The text was updated successfully, but these errors were encountered: