Checking Production Readiness
Liferay DXP 2026.Q3+
The Production Readiness tab on the Server Administration page reports how your running instance’s configuration compares against Liferay’s production deployment recommendations. Each validation is a single check against one recommendation.
To see your instance’s status, navigate to Control Panel → System → Server Administration → Production Readiness.
The dashboard recalculates results each time the page loads and when a validation is ignored or unignored. Because most validations check portal properties and JVM arguments, a change to one of those settings appears only after you restart the server.
Reading the Dashboard
Summary: The Summary header shows the total number of validations, followed by the Passed, Failed, and Ignored counts.
Category Sections: Validations are grouped into collapsible category sections. Click a category heading to collapse it. For a description of each category, see Production Readiness Categories.
Validation Rows: Each row shows a status icon, the validation’s name, and a status label reading Passed, Failed, or Ignored. Failing rows also show an explanatory message, an optional Current Value, and an optional Recommended Value. Passing rows and ignored rows show no message or values. Ignored rows are dimmed.
Filtering Validations
Click All Validations, Passed, Failed, or Ignored in the Filters group to narrow the visible rows. Only one filter is active at a time, so selecting a different filter replaces the current one. Click All Validations to restore the full list. Categories with no matching validations are hidden. Use Failed to evaluate differences from the recommendations, then Ignored to review what you’ve set aside.
Ignoring Validations
When a validation doesn’t apply to your environment, click Ignore (
) on a row to move that validation out of the Passed or Failed count and into Ignored. Click Unignore (
) to return it to the Passed or Failed count.
Working Through Failed Validations
Most of the settings these validations check are defined in server configuration files rather than in the Control Panel. Portal properties are set in an override file such as portal-ext.properties, described in the portal properties reference. JVM arguments are set in the application server’s startup environment, described in JVM Configuration. Changes to either take effect only when the server restarts.
On Liferay PaaS, portal properties go in the Liferay service’s configs directory and JVM arguments are set with the LIFERAY_JVM_OPTS environment variable, and both take effect on the next deployment. See Configuring the Liferay DXP Service and Liferay Service Environment Variables.
To resolve a failing validation:
-
Click Failed to list the validations that differ from the recommendations.
-
Read the row’s message and its optional Current Value and Recommended Value.
-
Change the setting in its configuration file or startup argument.
-
Restart the server.
-
Return to Control Panel → System → Server Administration → Production Readiness.
The row’s status label reads Passed only when the setting meets the recommendation. If it still fails, check the row’s message and any values it reports to see whether the change took effect.
For tuning information beyond these validations, see Tuning Liferay and Tuning Your JVM.
Production Readiness Categories
Validations are grouped by the part of the deployment they check.
| Category | Description |
|---|---|
| Database Configuration | Database connection pool sizing relative to the Tomcat thread pool |
| JVM and Infrastructure Validation | JVM startup arguments and application server settings, including garbage collection, heap sizing, huge pages, JMX, JSP engine settings, and diagnostic options |
| Portal Properties Configuration | Portal properties that affect production performance, storage, security, locales, and development-mode behavior |
| Search Engine Connectivity Validation | Whether the search engine runs in production mode rather than Sidecar mode |
Search Engine Connectivity Validation is the exception to the restart rule, because it checks the Elasticsearch connector’s configuration rather than a portal property or JVM argument. To resolve Sidecar Elasticsearch Detection, connect Liferay DXP to a standalone Elasticsearch cluster, then enable Production Mode in Control Panel → Configuration → System Settings → Search → Elasticsearch 8. The change takes effect without a server restart.
Two validations require Tomcat. JSP Engine Settings reads Tomcat’s JSP engine configuration, and Database Pool vs. Tomcat Thread Size compares the database connection pool against Tomcat’s thread pool. On other application servers, neither validation runs and the Database Configuration category is hidden.