KB-1009 "Could not find datasource" error thrown during JBoss startup

Jordan Horwat — Mon, 15 Oct 2018 13:51:04 GMT

Current Revision posted to Appian Knowledge Base by Jordan Horwat on 10/15/2018 1:51:04 PM

Symptoms

In some instances, JBoss fails to start up and the login page is not displayed when attempting to access Appian. In addition, the application server log contains the following message:

Could not find datasource: jdbc/AppianPrimaryDS
...
javax.naming.NameNotFoundException: jdbc/AppianPrimaryDS

Cause

JBoss

The custom.properties file is using a JNDI name that is not in the appian-ds.xml file. The data source details may not be configured in appian-ds.xml file at all.
The custom.properties file is using a JNDI name that does not match what is in the appian-ds.xml file. There could be a spelling error.
Either the custom.properties file or the appian-ds.xml file is using Java context (but not both), causing the inconsistency.
JBoss did not deploy the appian-ds.xml file due to the presence of either an appian-ds.xml.failed or appian-ds.xml.undeployed marker file in the <JBOSS_HOME>/standalone/deployments folder.

To confirm if JBoss is not deploying the data source properly, check for the following message in the application server log:

JBAS010400: Bound data source [java:/jdbc/AppianPrimaryDS]

If this message is not present, it means that the appian-ds.xml file is not visible to Appian and it was never deployed to JBoss. In this case, it does not matter whether or not the JNDI names in custom.properties and appian-ds.xml match.

Tomcat

The custom.properties file is using a JNDI name that is not in the suite.xml file. The data source details may not be configured in suite.xml file at all.
The custom.properties file is using a JNDI name that does not match what is in the suite.xml file. There could be a spelling error.
Either the custom.properties file or the suite.xml file is using Java context (but not both), causing the inconsistency.

Action

JBoss

Stop JBoss.
Stop the Appian engines.
Make sure the appian-ds.xml.dodeploy file is present in <JBOSS_HOME>/standalone/deployments.
Verify the names are correct in both custom.properties and appian-ds.xml.
In <JBOSS_HOME>/standalone/deployments, check to see if there is an appian-ds.xml.failed or appian-ds.xml.undeployed file. If there is, rename it to appian-ds.xml.dodeploy.
In <APPIAN_HOME>/ear, check to see if there is an suite.ear.failed file. If there is, rename it to suite.ear.dodeploy.
Start the Appian engines.
Start JBoss.

Tomcat

Stop Tomcat.
Stop the Appian engines.
Verify the names are correct in both custom.properties and suite.xml. If you plan to use the configure script to deploy configuration from repo to <APPIAN_HOME>, ensure that the datasource name is correct in tomcatResouce.xml.<ENVIRONMENT_NAME> file.
Start the Appian engiens.
Start Tomcat.

Affected Versions

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

Last Reviewed: October 2018

Tags: database, installation, application server, infrastructure

KB-1009 "Could not find datasource" error thrown during JBoss startup

Jordan Horwat — Mon, 15 Oct 2018 13:50:21 GMT

Revision 4 posted to Appian Knowledge Base by Jordan Horwat on 10/15/2018 1:50:21 PM

Symptoms

In some instances, JBoss fails to start up and the login page is not displayed when attempting to access Appian. In addition, the application server log contains the following message:

Could not find datasource: jdbc/AppianPrimaryDS
...
javax.naming.NameNotFoundException: jdbc/AppianPrimaryDS

Cause

JBoss

The custom.properties file is using a JNDI name that is not in the appian-ds.xml file. The data source details may not be configured in appian-ds.xml file at all.
The custom.properties file is using a JNDI name that does not match what is in the appian-ds.xml file. There could be a spelling error.
Either the custom.properties file or the appian-ds.xml file is using Java context (but not both), causing the inconsistency.
JBoss did not deploy the appian-ds.xml file due to the presence of either an appian-ds.xml.failed or appian-ds.xml.undeployed marker file in the <JBOSS_HOME>/standalone/deployments folder.

To confirm if JBoss is not deploying the data source properly, check for the following message in the application server log:

JBAS010400: Bound data source [java:/jdbc/AppianPrimaryDS]

Tomcat

The custom.properties file is using a JNDI name that is not in the suite.xml file. The data source details may not be configured in suite.xml file at all.
The custom.properties file is using a JNDI name that does not match what is in the suite.xml file. There could be a spelling error.
Either the custom.properties file or the suite.xml file is using Java context (but not both), causing the inconsistency.

Action

JBoss

To resolve the issue:

Stop JBoss.
Stop the Appian engines.
Make sure the appian-ds.xml.dodeploy file is present in <JBOSS_HOME>/standalone/deployments.
Verify the names are correct in both custom.properties and appian-ds.xml.
In <JBOSS_HOME>/standalone/deployments, check to see if there is an appian-ds.xml.failed or appian-ds.xml.undeployed file. If there is, rename it to appian-ds.xml.dodeploy.
In <APPIAN_HOME>/ear, check to see if there is an suite.ear.failed file. If there is, rename it to suite.ear.dodeploy.
Start the Appian engines.
Start JBoss.

Tomcat

Stop Tomcat.
Stop the Appian engines.
Verify the names are correct in both custom.properties and suite.xml. If you plan to use the configure script to deploy configuration from repo to <APPIAN_HOME>, ensure that the datasource name is correct in tomcatResouce.xml.<ENVIRONMENT_NAME> file.
Start the Appian engiens.
Start Tomcat.

Affected Versions

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

Last Reviewed: October 2018

Tags: database, installation, application server, infrastructure

KB-1009 "Could not find datasource" error thrown during JBoss startup

Jordan Horwat — Mon, 15 Oct 2018 13:50:00 GMT

Revision 3 posted to Appian Knowledge Base by Jordan Horwat on 10/15/2018 1:50:00 PM

Symptoms

In some instances, JBoss fails to start up and the login page is not displayed when attempting to access Appian. In addition, the application server log contains the following message:

Could not find datasource: jdbc/AppianPrimaryDS
...
javax.naming.NameNotFoundException: jdbc/AppianPrimaryDS

Cause

The following are possible causes for this issue:

JBoss

The custom.properties file is using a JNDI name that is not in the appian-ds.xml file. The data source details may not be configured in appian-ds.xml file at all.
The custom.properties file is using a JNDI name that does not match what is in the appian-ds.xml file. There could be a spelling error.
Either the custom.properties file or the appian-ds.xml file is using Java context (but not both), causing the inconsistency.
JBoss did not deploy the appian-ds.xml file due to the presence of either an appian-ds.xml.failed or appian-ds.xml.undeployed marker file in the <JBOSS_HOME>/standalone/deployments folder.

To confirm if JBoss is not deploying the data source properly, check for the following message in the application server log:

JBAS010400: Bound data source [java:/jdbc/AppianPrimaryDS]

Tomcat

The custom.properties file is using a JNDI name that is not in the suite.xml file. The data source details may not be configured in suite.xml file at all.
The custom.properties file is using a JNDI name that does not match what is in the suite.xml file. There could be a spelling error.
Either the custom.properties file or the suite.xml file is using Java context (but not both), causing the inconsistency.

Action

JBoss

To resolve the issue:

Stop JBoss.
Stop the Appian engines.
Make sure the appian-ds.xml.dodeploy file is present in <JBOSS_HOME>/standalone/deployments.
Verify the names are correct in both custom.properties and appian-ds.xml.
In <JBOSS_HOME>/standalone/deployments, check to see if there is an appian-ds.xml.failed or appian-ds.xml.undeployed file. If there is, rename it to appian-ds.xml.dodeploy.
In <APPIAN_HOME>/ear, check to see if there is an suite.ear.failed file. If there is, rename it to suite.ear.dodeploy.
Start the Appian engines.
Start JBoss.

Tomcat

Stop Tomcat.
Stop the Appian engines.
Verify the names are correct in both custom.properties and suite.xml. If you plan to use the configure script to deploy configuration from repo to <APPIAN_HOME>, ensure that the datasource name is correct in tomcatResouce.xml.<ENVIRONMENT_NAME> file.
Start the Appian engiens.
Start Tomcat.

Affected Versions

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

Last Reviewed: October 2018

Tags: database, installation, application server, infrastructure

KB-1009 "Could not find datasource" error thrown during JBoss startup

Parmida Borhani — Mon, 30 Jul 2018 04:12:50 GMT

Revision 2 posted to Appian Knowledge Base by Parmida Borhani on 7/30/2018 4:12:50 AM

Symptoms

In some instances, JBoss fails to start up and the login page is not displayed when attempting to access Appian. In addition, the application server log contains the following message:

Could not find datasource: jdbc/AppianPrimaryDS
...
javax.naming.NameNotFoundException: jdbc/AppianPrimaryDS

Cause

The following are possible causes for this issue:

The custom.properties file is using a JNDI name that is not in the appian-ds.xml file. The data source details may not be configured in appian-ds.xml file at all.
The custom.properties file is using a JNDI name that does not match what is in the appian-ds.xml file. There could be a spelling error.
Either the custom.properties file or the appian-ds.xml file is using Java context (but not both), causing the inconsistency.
JBoss did not deploy the appian-ds.xml file due to the presence of either an appian-ds.xml.failed or appian-ds.xml.undeployed marker file in the <JBOSS_HOME>/standalone/deployments folder.

To confirm if JBoss is not deploying the data source properly, check for the following message in the application server log:

JBAS010400: Bound data source [java:/jdbc/AppianPrimaryDS]

Action

To resolve the issue:

Stop JBoss.
Stop the Appian engines.
Make sure the appian-ds.xml.dodeploy file is present in <JBOSS_HOME>/standalone/deployments.
Verify the names are correct in both custom.properties and appian-ds.xml.
In <JBOSS_HOME>/standalone/deployments, check to see if there is an appian-ds.xml.failed or appian-ds.xml.undeployed file. If there is, rename it to appian-ds.xml.dodeploy.
In <APPIAN_HOME>/ear, check to see if there is an suite.ear.failed file. If there is, rename it to suite.ear.dodeploy.
Start the Appian engines.
Start JBoss.

Affected Versions

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

Last Reviewed: February 2017

Tags: database, installation, application server, infrastructure

KB-1009 "Could not find datasource" error thrown during JBoss startup

Nick Vigilante — Thu, 09 Feb 2017 22:41:59 GMT

Revision 1 posted to Appian Knowledge Base by Nick Vigilante on 2/9/2017 10:41:59 PM

Symptoms

In some instances, JBoss fails to start up and the login page is not displayed when attempting to access Appian. In addition, the application server log contains the following message:

Could not find datasource: jdbc/AppianPrimaryDS
...
javax.naming.NameNotFoundException: jdbc/AppianPrimaryDS

Cause

The following are possible causes for this issue:

The custom.properties file is using a JNDI name that is not in the appian-ds.xml file. The data source details may not be configured in appian-ds.xml file at all.
The custom.properties file is using a JNDI name that does not match what is in the appian-ds.xml file. There could be a spelling error.
Either the custom.properties file or the appian-ds.xml file is using Java context (but not both), causing the inconsistency.
JBoss did not deploy the appian-ds.xml file due to the presence of either an appian-ds.xml.failed or appian-ds.xml.undeployed marker file in the <JBOSS_HOME>/standalone/deployments folder.

To confirm if JBoss is not deploying the data source properly, check for the following message in the application server log:

JBAS010400: Bound data source [java:/jdbc/AppianPrimaryDS]

Action

To resolve the issue:

Stop JBoss.
Stop the Appian engines.
Make sure the appian-ds.xml.dodeploy file is present in <JBOSS_HOME>/standalone/deployments.
Verify the names are correct in both custom.properties and appian-ds.xml.
In <JBOSS_HOME>/standalone/deployments, check to see if there is an appian-ds.xml.failed or appian-ds.xml.undeployed file. If there is, rename it to appian-ds.xml.dodeploy.
In <APPIAN_HOME>/ear, check to see if there is an suite.ear.failed file. If there is, rename it to suite.ear.dodeploy.
Start the Appian engines.
Start JBoss.

Affected Versions

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

Last Reviewed: February 2017

Tags: database, application server