[MGNLXAA-47] Allow for automatic expiration of transaction lock - port to 1.3 Created: 09/Jul/12  Updated: 21/May/13  Resolved: 15/Aug/12

Status: Closed
Project: Transactional Activation
Component/s: None
Affects Version/s: 1.3.2
Fix Version/s: 1.3.4

Type: New Feature Priority: Major
Reporter: Jan Haderka Assignee: Milan Divilek
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Cloners
clones MGNLXAA-46 Allow for automatic expiration of tra... Closed
causality
relation
is related to MGNLXAA-29 CLONE -Session issuing the lock is no... Closed
Template:
Acceptance criteria:
Empty

 Description   

While this should be rather exceptional situation, it is possible for public instance to be temporarily unavailable for second phase of transaction resulting in failure to finish such transaction. Until now this situation have been treated as critical failure and forcing administrator to initiate manual cleanup of content under such failed transaction in order to restore operations. In order to expedit processing in less stable environments, such condition will be now treated as recoverable error - Magnolia will automatically expire locks on such content in configurable time interval (by default within 15 minutes).
To configure such interval to different then default value please set transactionExpireSeconds property of XAReceiveFilter under /server/filters/activation to desired value (default is 900).



 Comments   
Comment by Jan Haderka [ 25/Jul/12 ]

Moving to next version w/ increased priority to make sure this port is not postponed any longer. Please reset priority once this issue is fixed.

Generated at Mon Feb 12 11:06:33 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.