Control Hub On-Prem component page does not load correctly, yields “Http failure response” error at bottom of page.

Problem

Opening a Control Hub component app such as Connections or Jobs yields a page which contains only the header of the page, with an error message appearing briefly at the bottom of the page as shown in Figure 1 below.

This problem is most likely to be encountered after upgrading Control Hub from an older (before 3.19.0) version.

Figure 1: Connections Page not loading properly

Cause

The component (application) is not being started with Control Hub.

Solution

Verify that the Control Hub component which fails to load correctly is listed among the apps to start in $DPM_CONF/dpm.properties.

In this configuration file, find the apps.to.start property.  It should look something like this:

apps.to.start=security,pipelinestore,messaging,jobrunner,timeseries,topology,notification,sla,provisioning,scheduler,reporting,sdp_classification,policy,dynamic_preview,connection

This property lists the Control Hub components which will be started with Control Hub.

The contents of this property depend on your Control Hub version.  Consult the table below, and add any missing entries to the list in the apps.to.start property.  Restart Control Hub for the changes to take effect.