[MGNLUI-1793] Ensure session unlock when dealing with messages in MagnoliaShell. Created: 27/Jun/13  Updated: 27/Jun/13  Resolved: 27/Jun/13

Status: Closed
Project: Magnolia UI
Component/s: None
Affects Version/s: 5.0.1
Fix Version/s: 5.0.1

Type: Bug Priority: Critical
Reporter: Aleksandr Pchelintcev Assignee: Aleksandr Pchelintcev
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to MGNLUI-1145 The messaging subsystem is too much b... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

Session should be unlocked in a 'finally' clause to make sure it doesn't stay locked in case message-dispatching method fails at some point.



 Comments   
Comment by Christopher Zimmermann [ 27/Jun/13 ]

https://git.magnolia-cms.com/gitweb/?p=magnolia_ui.git;a=commitdiff;h=e0abb1c81958f5b40f1cfe981d7e87f4385f4112
DIFF.
"MGNLUI-1145 Ensuring session.unlock() call by making it in a finally clause."

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