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

Jordan Horwat — Mon, 23 Jul 2018 17:48:39 GMT

Current Revision posted to Appian Knowledge Base by Jordan Horwat on 7/23/2018 5:48:39 PM

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.

Tags: installation, application server, infrastructure, jboss

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

Nick Vigilante — Fri, 17 Mar 2017 17:52:09 GMT

Revision 4 posted to Appian Knowledge Base by Nick Vigilante on 3/17/2017 5:52:09 PM

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.

Tags: application server, jboss

"Error looking up jdbc/, service service jboss.naming.context.java.jdbc. is not started"

Khalil Ben Naceur — Fri, 17 Mar 2017 17:40:27 GMT

Revision 1 posted to Appian Knowledge Base by Khalil Ben Naceur on 3/17/2017 5:40:27 PM

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 Application Server.

Tags: application server, jboss

"Error looking up jdbc/, service service jboss.naming.context.java.jdbc. is not started"

Khalil Ben Naceur — Fri, 17 Mar 2017 13:50:00 GMT

Revision 3 posted to Appian Knowledge Base by Khalil Ben Naceur on 3/17/2017 1:50:00 PM

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 Application Server.

Tags: application server, jboss

"Error looking up jdbc/, service service jboss.naming.context.java.jdbc. is not started"

Khalil Ben Naceur — Fri, 17 Mar 2017 13:48:57 GMT

Revision 2 posted to Appian Knowledge Base by Khalil Ben Naceur on 3/17/2017 1:48:57 PM

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 Application Server.

Tags: application server, jboss