Controlling the Startup Block Mechanism

Owned by Matthew Wagner
Last updated: Aug 04, 2020
1 min read

By default, XperienCentral blocks login requests from the frontend and backend while it is starting up. When you try to log in from the frontend or backend while XperienCentral is still in the startup phase, the following message displays:





If you want to suppress this message, follow these steps:

  1. Add the following JAVA_OPTS property to the beginning of the XperienCentral block:

    -Dwebmanager.startupblock.skip=true

    For example:

    set JAVA_OPTS=%JAVA_OPTS% -Dwebmanager.startupblock.skip=true -Djava.awt.headless=true -Dwebmanager.jcr.filemirror=true -Dwebmanager.clustering.readonly=false -Xms512m -Xmx512m –Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=8000

    When blocking is turned off, requests from the frontend will return a cached version of the requested page or a white page with no content when XperienCentral has not finished the startup process, Requests from the backend will show the XperienCentral login screen, however you will not be able to log in.

  2. To enable the startup block mechanism, change the true declaration to false. For example:

    -Dwebmanager.startupblock.skip=false