-
Bug
-
Resolution: Fixed
-
Blocker
-
5.2
-
None
After starting one or more long running actions, user becomes blocked in given browser session. Logout/Login doesn't help. Logging in as same user in different browser allows user to interact w/ server again. UI becomes "unlocked" and responsive again once the long running action is finished.
Problem is more pronounced with Firefox and Chrome then with Safari. Didn't test on IE.
While server became very "sluggish" at some point due to number of running actions, our tests didn't confirm ability to completely bring down the server at this point.
The issue was not reproducible at all in Magnolia 5.0 using older version of Vaadin, which suggests issue is related to some change (probably introduction of locks) in Vaadin 7.1.
More details discussed/described at http://wiki.magnolia-cms.com/display/DEV/Concept+-+Long+running+actions+intermediate+solution
- depends upon
-
MGNLWORKFLOW-222 Hardcoded values in WorkflowFormDialogPresenter.configureDialogActions(FormDialogDefinition)
- Closed
-
MGNLEE-358 Re-Add module scheduler to ee_bundle
- Closed
- is causing
-
MGNLUI-2855 Ansynchonous action (activation) should return better error message
- Closed
- is depended upon by
-
DEAD-7 Deadlink module causes weird vaadin effects
- Open
-
MGNLUI-1901 Asynchron Actions
- Closed
- is related to
-
MGNLDAM-441 (Potentially) long running actions should be configured to run asynchronously
- Closed
-
MGNLUI-2840 (Potentially) long running actions should be configured to run asynchronously
- Closed
-
MGNLWORKFLOW-242 Enable workflow to run activation asynchronously after approval & publish
- Closed
- mentioned in
-
Wiki Page Loading...