-
Type:
Improvement
-
Status: Resolved
-
Priority:
Critical
-
Resolution: Won't Fix
-
Affects Version/s: None
-
Fix Version/s: 3.20.1
-
Component/s: Technical / Transverse
-
Tags:
-
Story Points:2
The current Status Servlet has two possible OK response:
- Servlet loaded: basically Tomcat stated.
- Runtime started: basically components loaded but not started.
Issue is Runtime started doesn't mean all the components are correctly started. For instance, database and ACL vacuuming not done.
In the context of a cluster, especially with NOS, we identified in NXCONNECT-2182 that it could lead to having node blocked at startup. (Trying to read ACL because of a query when vacuuming is in progress)
We are overriding the current StatusServlet for having a OK state at the end of all components.