KB-1308 "Error looking up jdbc/<JNDI_NAME>, service service jboss.naming.context.java.jdbc.<JNDI_NAME> is not started"

Symptoms

When starting JBoss Application Server, the following error message is returned in the application server log:

 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/suite]] (ServerService Thread Pool -- 132) JBWEB000287: Exception sending context initialized event to listener instance of class com.appiancorp.rdbms.datasource.BusinessDataSourceValidator: com.appiancorp.common.config.FatalConfigurationException: com.appiancorp.suiteapi.common.exceptions.AppianException: com.appiancorp.rdbms.datasource.DataSourceException: javax.naming.NameNotFoundException: Error looking up jdbc/<JNDI_NAME>, service service jboss.naming.context.java.jdbc.<JNDI_NAME> is not started
 ...
 Caused by: com.appiancorp.rdbms.datasource.DataSourceException: javax.naming.NameNotFoundException: Error looking up jdbc/<JNDI_NAME>, service service jboss.naming.context.java.jdbc.SqlServer is not started
 ...
 Caused by: javax.naming.NameNotFoundException: Error looking up jdbc/<JNDI_NAME>, service service jboss.naming.context.java.jdbc.SqlServer is not started
 ...
 Caused by: javax.naming.NameNotFoundException: Error looking up jdbc/<JNDI_NAME>, service service jboss.naming.context.java.jdbc.SqlServer is not started

The application server then fails to start up.

Cause

The <driver> block was not added for this database vendor in standalone.xml, located in the <JBOSS_HOME>/standalone/configuration directory.

Action

Follow the steps in the documentation to configure relational databases, and add the <driver> block in standalone.xml.

Affected Versions

This article applies to all versions of Appian using JBoss EAP as an application server.