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
I'm upgrading our rebus instance from 6.7.0 to 8.4.2 to make use of the open telemetry extensions but have hit a bit of a wall.
We use a custom IExclusiveAccessLock implementation that uses MSSQL to create and store the locks, but with the changes in 7.0.0 to the payload parameter in AquireLockAsync from
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi All,
I'm upgrading our rebus instance from 6.7.0 to 8.4.2 to make use of the open telemetry extensions but have hit a bit of a wall.
We use a custom IExclusiveAccessLock implementation that uses MSSQL to create and store the locks, but with the changes in 7.0.0 to the payload parameter in
AquireLockAsync
from{ "SagaDataType": "TypeX", "CorrelationPropertyName": "TypeX.PropY", "CorrelationPropertyValue": "Value" }
to
sagalock_<int>
our custom implementation has obviously stopped working.Does anyone have any guidance on how to use the new payload to ensure correct exclusive locking?
Beta Was this translation helpful? Give feedback.
All reactions