-
Bug
-
Resolution: Fixed
-
Neutral
-
6.2.38
-
None
-
-
Empty show more show less
-
Yes
-
Nucleus 47
-
3
-
Yes
USer Story: users are experiencing sporadic failures during the startup of Magnolia instances, specifically on faster machines. The issue is related to a delay in applying server configuration or order of applying certain part of the configuration. This started to appear after the upgrade to Magnolia version 6.2.38, although previous versions also can be affected
Â
As described here: https://magnolia-cms.slack.com/archives/CC1GVEGFP/p1694701640514539
TL;DR (apchelintcev)
as I see it - the problem is that core brings in the correct server config, but there’s a 1 second gap before it is applied and new beans are produced on its basis, which may become visible on the newer/faster machines
re: fix - guess we could slash the delay during the install time to smth really small, and/or manually re-trigger the sensitive beans directly from core module installation phase
Dev note:
- to reproduce the issue steadily change this delay to 5000.
- is cloned by
-
MAGNOLIA-9214 Instances randomly fail to start up on fast machines
- Closed
- relates to
-
MAGNOLIA-6593 resource-loader module throws NPE upon clean install when using the empty-webapp
- Closed
-
MAGNOLIA-9259 Magnolia fails to start with error ’javax.jcr.PathNotFoundException: /system`
- Open
-
MGNLDIFF-146 Revise permissions to diff with modular privilege pattern
- Closed
1.
|
Implementation | Completed | AntonĂn Juran | |
2.
|
Review | Completed | Jaromir Sarf | |
3.
|
Pre-integration QA | Completed | Jaromir Sarf | |
4.
|
Final QA | Completed | Quach Hao Thien |