Tomcat is able to start successfully, but one or both of the following warnings are seen in <APPIAN_HOME>/logs/tomcat-stdOut.log:
<APPIAN_HOME>/logs/tomcat-stdOut.log
WARN com.appiancorp.suite.SuiteConfiguration - Misconfigured STATIC_SERVER_AND_PORT property in custom.properties - The static content hostname cannot use the same domain as SERVER_AND_PORT or DYNAMIC_SERVER_AND_PORT. Some Appian features will not be available.WARN com.appiancorp.suite.SuiteConfiguration - Misconfigured DYNAMIC_SERVER_AND_PORT property in custom.properties - The dynamic content hostname cannot use the same domain as SERVER_AND_PORT or STATIC_SERVER_AND_PORT. Some Appian features will not be available.
One or both of the following fields are not configured properly in <APPIAN_HOME>/conf/custom.properties:
<APPIAN_HOME>/conf/custom.properties
conf.suite.STATIC_SERVER_AND_PORT
conf.suite.DYNAMIC_SERVER_AND_PORT
Common misconfigurations include:
conf.suite.STATIC_SERVER_AND_PORT/
conf.suite.SERVER_AND_PORT
conf.suite.SERVER_AND_PORT=subdomain.domain.com conf.suite.STATIC_SERVER_AND_PORT=subdomain-static.domain.com conf.suite.DYNAMIC_SERVER_AND_PORT=subdomain-dynamic.domain.com
Ensure the URL domains in conf.suite.STATIC_SERVER_AND_PORT, conf.suite.DYNAMIC_SERVER_AND_PORT, and conf.suite.SERVER_AND_PORT are all unique.
For more information about these fields, read the Configuring Static and Dynamic Content URLs section in the Post-Install Configurations documentation.
This article applies to Appian 18.3 and later.
Last Reviewed: December 2018