Issues

Select view

Select search mode

 
27 of 27

A failed version check will render the session unusea

Rejected

Description

If the optimistic locking version check fails, the version checking BeforeTransactionCompletionProcess is not removed from the action queue, so if I try to commit another transaction in the same session, the version check will fail again, and therefor the whole session can't be used for writing any more.

Simplest solution would probbly be clearing the BeforeTransactionCompletionProcess and AfterTransactionCompletionProcess (I'm quite sure they'll queues in the ActionQueue.clear() method.

Details

Assignee

Reporter

Labels

Affects versions

Priority

Created September 5, 2014 at 10:12 PM
Updated April 22, 2015 at 9:14 PM
Resolved September 5, 2014 at 11:52 PM

Activity

Show:

Brett Meyer April 22, 2015 at 9:14 PM

Closing rejected issues.

Former user September 5, 2014 at 11:52 PM

This is expected behavior.

felixtreede September 5, 2014 at 10:16 PM

Sorry, it seems that I screwed up the last description sentence. It should say: "Simplest solution would probbly be clearing the BeforeTransactionCompletionProcess and AfterTransactionCompletionProcess queues in the ActionQueue.clear() method."