Skip to content

ConcurrenctionException can not be Catched #17423

Closed Answered by ayende
sbgmk asked this question in Q&A
Discussion options

You must be logged in to vote

Are you using the same session again? Once you got ConcurrencyExcpetion you should create a new session.

If you are calling SaveChangesAsync in the middleware, it does the same operation, and it will fail again.

You can call session.Advanced.Clear() to reset the entire state, so the middleware call with be a noop.

Replies: 1 comment 1 reply

Comment options

You must be logged in to vote
1 reply
@sbgmk
Comment options

Answer selected by sbgmk
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants