KB-1718 Tomcat fails to deploy Appian or start all services successfully

James Lee — Tue, 11 Aug 2020 21:10:58 GMT

Current Revision posted to Appian Knowledge Base by James Lee on 8/11/2020 9:10:58 PM

Symptoms

Symptom 1

Tomcat fails with the following error in <APPIAN_HOME>/logs/tomcat-stdOut.log:

ERROR org.hibernate.connection.DatasourceConnectionProvider - Could not find datasource: jdbc/AppianDS
javax.naming.NameNotFoundException: Name [jdbc/AppianDS] is not bound in this Context. Unable to find [jdbc].

Symptom 2

Tomcat starts successfully, but the Appian suite is not started. Although there is no explicit error in the tomcat-stdOut.log, the log output is much shorter than a typical start-up:

The system cannot find the file c:\appian\conf\custom.properties.
Using CATALINA_BASE:   "C:\appian\tomcat\apache-tomcat"
Using CATALINA_HOME:   "C:\appian\tomcat\apache-tomcat"
Using CATALINA_TMPDIR: "C:\appian\tomcat\apache-tomcat\temp"
Using JRE_HOME:        "C:\appian\java\jre"
Using CLASSPATH:       "C:\appian\tomcat\apache-tomcat\bin\bootstrap.jar;C:\appian\tomcat\apache-tomcat\bin\tomcat-juli.jar"
2019-05-15 19:39:24.082 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server version:        Apache Tomcat/8.5.40
2019-05-15 19:39:24.086 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server built:          Apr 10 2019 14:31:19 UTC
2019-05-15 19:39:24.087 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server number:         8.5.40.0
2019-05-15 19:39:24.087 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log OS Name:               Windows Server 2016
2019-05-15 19:39:24.087 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log OS Version:            10.0
2019-05-15 19:39:24.087 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Architecture:          amd64
2019-05-15 19:39:24.087 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Java Home:             C:\appian\java\jre
2019-05-15 19:39:24.087 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log JVM Version:           1.8.0_192-b12
2019-05-15 19:39:24.087 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log JVM Vendor:            Oracle Corporation
2019-05-15 19:39:24.087 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log CATALINA_BASE:         C:\appian\tomcat\apache-tomcat
2019-05-15 19:39:24.087 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log CATALINA_HOME:         C:\appian\tomcat\apache-tomcat
2019-05-15 19:39:24.090 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.util.logging.config.file=C:\appian\tomcat\apache-tomcat\conf\logging.properties
2019-05-15 19:39:24.090 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
2019-05-15 19:39:24.090 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djdk.tls.ephemeralDHKeySize=2048
2019-05-15 19:39:24.090 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.protocol.handler.pkgs=org.apache.catalina.webresources
2019-05-15 19:39:24.090 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dfile.encoding=UTF-8
2019-05-15 19:39:24.090 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Duser.timezone=GMT
2019-05-15 19:39:24.091 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.naming.factory.initial=com.appiancorp.tomcat.naming.TomcatInitialContextFactory
2019-05-15 19:39:24.091 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.awt.headless=true
2019-05-15 19:39:24.091 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.net.preferIPv4Stack=true
2019-05-15 19:39:24.091 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dorg.osgi.framework.security=osgi
2019-05-15 19:39:24.091 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.security.manager
2019-05-15 19:39:24.091 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dsun.net.inetaddr.ttl=60
2019-05-15 19:39:24.091 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dsun.rmi.dgc.client.gcInterval=3600000
2019-05-15 19:39:24.091 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dsun.rmi.dgc.server.gcInterval=3600000
2019-05-15 19:39:24.091 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:+UseCompressedOops
2019-05-15 19:39:24.091 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:-TieredCompilation
2019-05-15 19:39:24.091 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:ReservedCodeCacheSize=256M
2019-05-15 19:39:24.091 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:+UseConcMarkSweepGC
2019-05-15 19:39:24.092 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:+ExplicitGCInvokesConcurrent
2019-05-15 19:39:24.092 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:+CMSClassUnloadingEnabled
2019-05-15 19:39:24.092 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:-TraceClassUnloading
2019-05-15 19:39:24.092 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:+PrintGCDetails
2019-05-15 19:39:24.092 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:+PrintGCDateStamps
2019-05-15 19:39:24.092 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:+UseGCLogFileRotation
2019-05-15 19:39:24.092 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:NumberOfGCLogFiles=5
2019-05-15 19:39:24.092 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:GCLogFileSize=3M
2019-05-15 19:39:24.092 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:+HeapDumpOnOutOfMemoryError
2019-05-15 19:39:24.092 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -verbose:gc
2019-05-15 19:39:24.092 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dae.home=c:\appian
2019-05-15 19:39:24.092 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Xloggc:c:\appian\logs\tomcat\gc.log
2019-05-15 19:39:24.093 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Xms2048m
2019-05-15 19:39:24.093 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Xmx4096m
2019-05-15 19:39:24.093 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.security.policy=C:\appian\tomcat\apache-tomcat\conf\all.policy
2019-05-15 19:39:24.093 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dignore.endorsed.dirs=
2019-05-15 19:39:24.093 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dcatalina.base=C:\appian\tomcat\apache-tomcat
2019-05-15 19:39:24.093 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dcatalina.home=C:\appian\tomcat\apache-tomcat
2019-05-15 19:39:24.093 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.io.tmpdir=C:\appian\tomcat\apache-tomcat\temp
2019-05-15 19:39:24.835 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["http-nio-8080"]
2019-05-15 19:39:24.967 INFO [main] org.apache.tomcat.util.net.NioSelectorPool.getSharedSelector Using a shared selector for servlet write/read
2019-05-15 19:39:24.997 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["ajp-nio-8009"]
2019-05-15 19:39:25.002 INFO [main] org.apache.tomcat.util.net.NioSelectorPool.getSharedSelector Using a shared selector for servlet write/read
2019-05-15 19:39:25.002 INFO [main] org.apache.catalina.startup.Catalina.load Initialization processed in 1475 ms
2019-05-15 19:39:25.022 INFO [main] org.apache.catalina.core.StandardService.startInternal Starting service [Catalina]
2019-05-15 19:39:25.022 INFO [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet Engine: Apache Tomcat/8.5.40
2019-05-15 19:39:25.140 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio-8080"]
2019-05-15 19:39:25.175 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["ajp-nio-8009"]
2019-05-15 19:39:25.179 INFO [main] org.apache.catalina.startup.Catalina.start Server startup in 175 ms

Cause

When the configure script is run, the content in tomcatResources.xml.<ENVIRONMENT> is copied to suite.xml in <APPIAN_HOME>\tomcat\apache-tomcat\conf\Catalina\localhost.

This error occurs if the content is not copied over correctly or if suite.xml is configured improperly.

Action

Ensure tomcatResources.xml.<ENVIRONMENT> is configured according to installation documentation and copy the entire contents of that file into suite.xml in between the lines:


Restart Tomcat.

Affected Versions

This article applies to Appian 18.3 and later.

Last Reviewed: August 2020

Tags: Tomcat, installation, application server, infrastructure

KB-1718 Tomcat fails to deploy Appian or start all services successfully

James Lee — Tue, 11 Aug 2020 21:09:19 GMT

Revision 18 posted to Appian Knowledge Base by James Lee on 8/11/2020 9:09:19 PM

Symptoms

Symptom 1

Tomcat fails with the following error in <APPIAN_HOME>/logs/tomcat-stdOut.log:

ERROR org.hibernate.connection.DatasourceConnectionProvider - Could not find datasource: jdbc/AppianDS
javax.naming.NameNotFoundException: Name [jdbc/AppianDS] is not bound in this Context. Unable to find [jdbc].

Symptom 2

Tomcat starts successfully, but the Appian suite is not started. Although there is no explicit error in the tomcat-stdOut.log, the log output is much shorter than a typical start-up:

The system cannot find the file c:\appian\conf\custom.properties.
Using CATALINA_BASE:   "C:\appian\tomcat\apache-tomcat"
Using CATALINA_HOME:   "C:\appian\tomcat\apache-tomcat"
Using CATALINA_TMPDIR: "C:\appian\tomcat\apache-tomcat\temp"
Using JRE_HOME:        "C:\appian\java\jre"
Using CLASSPATH:       "C:\appian\tomcat\apache-tomcat\bin\bootstrap.jar;C:\appian\tomcat\apache-tomcat\bin\tomcat-juli.jar"
2019-05-15 19:39:24.082 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server version:        Apache Tomcat/8.5.40
2019-05-15 19:39:24.086 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server built:          Apr 10 2019 14:31:19 UTC
2019-05-15 19:39:24.087 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server number:         8.5.40.0
2019-05-15 19:39:24.087 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log OS Name:               Windows Server 2016
2019-05-15 19:39:24.087 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log OS Version:            10.0
2019-05-15 19:39:24.087 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Architecture:          amd64
2019-05-15 19:39:24.087 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Java Home:             C:\appian\java\jre
2019-05-15 19:39:24.087 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log JVM Version:           1.8.0_192-b12
2019-05-15 19:39:24.087 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log JVM Vendor:            Oracle Corporation
2019-05-15 19:39:24.087 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log CATALINA_BASE:         C:\appian\tomcat\apache-tomcat
2019-05-15 19:39:24.087 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log CATALINA_HOME:         C:\appian\tomcat\apache-tomcat
2019-05-15 19:39:24.090 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.util.logging.config.file=C:\appian\tomcat\apache-tomcat\conf\logging.properties
2019-05-15 19:39:24.090 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
2019-05-15 19:39:24.090 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djdk.tls.ephemeralDHKeySize=2048
2019-05-15 19:39:24.090 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.protocol.handler.pkgs=org.apache.catalina.webresources
2019-05-15 19:39:24.090 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dfile.encoding=UTF-8
2019-05-15 19:39:24.090 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Duser.timezone=GMT
2019-05-15 19:39:24.091 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.naming.factory.initial=com.appiancorp.tomcat.naming.TomcatInitialContextFactory
2019-05-15 19:39:24.091 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.awt.headless=true
2019-05-15 19:39:24.091 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.net.preferIPv4Stack=true
2019-05-15 19:39:24.091 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dorg.osgi.framework.security=osgi
2019-05-15 19:39:24.091 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.security.manager
2019-05-15 19:39:24.091 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dsun.net.inetaddr.ttl=60
2019-05-15 19:39:24.091 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dsun.rmi.dgc.client.gcInterval=3600000
2019-05-15 19:39:24.091 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dsun.rmi.dgc.server.gcInterval=3600000
2019-05-15 19:39:24.091 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:+UseCompressedOops
2019-05-15 19:39:24.091 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:-TieredCompilation
2019-05-15 19:39:24.091 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:ReservedCodeCacheSize=256M
2019-05-15 19:39:24.091 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:+UseConcMarkSweepGC
2019-05-15 19:39:24.092 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:+ExplicitGCInvokesConcurrent
2019-05-15 19:39:24.092 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:+CMSClassUnloadingEnabled
2019-05-15 19:39:24.092 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:-TraceClassUnloading
2019-05-15 19:39:24.092 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:+PrintGCDetails
2019-05-15 19:39:24.092 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:+PrintGCDateStamps
2019-05-15 19:39:24.092 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:+UseGCLogFileRotation
2019-05-15 19:39:24.092 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:NumberOfGCLogFiles=5
2019-05-15 19:39:24.092 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:GCLogFileSize=3M
2019-05-15 19:39:24.092 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:+HeapDumpOnOutOfMemoryError
2019-05-15 19:39:24.092 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -verbose:gc
2019-05-15 19:39:24.092 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dae.home=c:\appian
2019-05-15 19:39:24.092 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Xloggc:c:\appian\logs\tomcat\gc.log
2019-05-15 19:39:24.093 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Xms2048m
2019-05-15 19:39:24.093 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Xmx4096m
2019-05-15 19:39:24.093 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.security.policy=C:\appian\tomcat\apache-tomcat\conf\all.policy
2019-05-15 19:39:24.093 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dignore.endorsed.dirs=
2019-05-15 19:39:24.093 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dcatalina.base=C:\appian\tomcat\apache-tomcat
2019-05-15 19:39:24.093 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dcatalina.home=C:\appian\tomcat\apache-tomcat
2019-05-15 19:39:24.093 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.io.tmpdir=C:\appian\tomcat\apache-tomcat\temp
2019-05-15 19:39:24.835 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["http-nio-8080"]
2019-05-15 19:39:24.967 INFO [main] org.apache.tomcat.util.net.NioSelectorPool.getSharedSelector Using a shared selector for servlet write/read
2019-05-15 19:39:24.997 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["ajp-nio-8009"]
2019-05-15 19:39:25.002 INFO [main] org.apache.tomcat.util.net.NioSelectorPool.getSharedSelector Using a shared selector for servlet write/read
2019-05-15 19:39:25.002 INFO [main] org.apache.catalina.startup.Catalina.load Initialization processed in 1475 ms
2019-05-15 19:39:25.022 INFO [main] org.apache.catalina.core.StandardService.startInternal Starting service [Catalina]
2019-05-15 19:39:25.022 INFO [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet Engine: Apache Tomcat/8.5.40
2019-05-15 19:39:25.140 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio-8080"]
2019-05-15 19:39:25.175 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["ajp-nio-8009"]
2019-05-15 19:39:25.179 INFO [main] org.apache.catalina.startup.Catalina.start Server startup in 175 ms

Cause

When the configure script is run, the content in tomcatResources.xml.<ENVIRONMENT> is copied to suite.xml in <APPIAN_HOME>\tomcat\apache-tomcat\conf\Catalina\localhost.

This error occurs if the content is not copied over correctly or if suite.xml is configured improperly.

Action

Ensure tomcatResources.xml.<ENVIRONMENT> is configured according to installation documentation and copy the entire contents of that file into suite.xml in between the lines:


Restart Tomcat.

Affected Versions

This article applies to Appian 18.3 and later.

Last Reviewed: August 2020

Tags: Tomcat, installation, application server, infrastructure

KB-1718 Tomcat fails to deploy Appian with "NameNotFoundException"

Jordan Horwat — Wed, 19 Sep 2018 17:06:29 GMT

Revision 17 posted to Appian Knowledge Base by Jordan Horwat on 9/19/2018 5:06:29 PM

Symptoms

Tomcat fails with the following error in <APPIAN_HOME>/logs/tomcat-stdOut.log:

ERROR org.hibernate.connection.DatasourceConnectionProvider - Could not find datasource: jdbc/AppianDS
javax.naming.NameNotFoundException: Name [jdbc/AppianDS] is not bound in this Context. Unable to find [jdbc].

Cause

When the configure script is run, the content in tomcatResources.xml.<ENVIRONMENT> is copied to suite.xml in <APPIAN_HOME>\tomcat\apache-tomcat\conf\Catalina\localhost.

This error occurs if this content does not copy over correctly or if suite.xml is configured improperly.

Action

Ensure tomcatResources.xml.<ENVIRONMENT> is configured according to installation documentation and manually copy the entire contents of it to suite.xml in between the lines:


Restart Tomcat.

Affected Versions

This article applies to Appian 18.3 and later.

Last Reviewed: September 2018

Tags: Tomcat, installation, application server, infrastructure

DRAFT KB-XXXX Tomcat fails to deploy Appian with "NameNotFoundException"

Jordan Horwat — Wed, 19 Sep 2018 13:05:11 GMT

Revision 16 posted to Appian Knowledge Base by Jordan Horwat on 9/19/2018 1:05:11 PM

Symptoms

Tomcat fails with the following error in <APPIAN_HOME>/logs/tomcat-stdOut.log:

ERROR org.hibernate.connection.DatasourceConnectionProvider - Could not find datasource: jdbc/AppianDS
javax.naming.NameNotFoundException: Name [jdbc/AppianDS] is not bound in this Context. Unable to find [jdbc].

Cause

When the configure script is run, the content in tomcatResources.xml.<ENVIRONMENT> is copied to suite.xml in <APPIAN_HOME>\tomcat\apache-tomcat\conf\Catalina\localhost.

This error occurs if this content does not copy over correctly or if suite.xml is configured improperly.

Action

Ensure tomcatResources.xml.<ENVIRONMENT> is configured according to installation documentation and manually copy the entire contents of it to suite.xml in between the lines:


Restart Tomcat.

Affected Versions

This article applies to Appian 18.3 and later.

Last Reviewed: September 2018

Tags: Tomcat, application server, infrastructure

DRAFT KB-XXXX Tomcat fails to deploy Appian with "NameNotFoundException"

Tejas Kargutkar — Tue, 18 Sep 2018 12:36:11 GMT

Revision 15 posted to Appian Knowledge Base by Tejas Kargutkar on 9/18/2018 12:36:11 PM

Symptoms

Tomcat fails with the following error in <APPIAN_HOME>/logs/tomcat-stdOut.log:

ERROR org.hibernate.connection.DatasourceConnectionProvider - Could not find datasource: jdbc/AppianDS
javax.naming.NameNotFoundException: Name [jdbc/AppianDS] is not bound in this Context. Unable to find [jdbc].

Cause

When the configure script is run, the content in tomcatResources.xml.<ENVIRONMENT> is copied to suite.xml in <APPIAN_HOME>\tomcat\apache-tomcat\conf\Catalina\localhost.

This error occurs if this content does not copy over correctly or if suite.xml is configured improperly.

Action

Ensure tomcatResources.xml.<ENVIRONMENT> is configured according to installation documentation and manually copy the entire contents of it to suite.xml in between the lines:


Restart Tomcat.

Affected Versions

This article applies to Appian 18.3 and later.

Last Reviewed: September 2018

Tags: Tomcat, application server, infrastructure

DRAFT KB-XXXX Tomcat fails with "Unable to find [jdbc]"

Rebecca Jonas — Tue, 18 Sep 2018 12:27:51 GMT

Revision 14 posted to Appian Knowledge Base by Rebecca Jonas on 9/18/2018 12:27:51 PM

Symptoms

Tomcat fails with the following error in <APPIAN_HOME>/logs/tomcat-stdOut.log:

ERROR org.hibernate.connection.DatasourceConnectionProvider - Could not find datasource: jdbc/AppianDS
javax.naming.NameNotFoundException: Name [jdbc/AppianDS] is not bound in this Context. Unable to find [jdbc].

Cause

When the configure script is run, the content in tomcatResources.xml.<ENVIRONMENT> is copied to suite.xml in <APPIAN_HOME>\tomcat\apache-tomcat\conf\Catalina\localhost.

This error occurs if this content does not copy over correctly or if suite.xml is configured improperly.

Action

Ensure tomcatResources.xml.<ENVIRONMENT> is configured according to installation documentation and manually copy the entire contents of it to suite.xml in between the lines:


Restart Tomcat.

Affected Versions

This article applies to Appian 18.3 and later.

Last Reviewed: September 2018

Tags: Tomcat, application server, infrastructure

DRAFT KB-XXXX Tomcat fails with "Unable to find [jdbc]"

Rebecca Jonas — Tue, 18 Sep 2018 12:25:49 GMT

Revision 13 posted to Appian Knowledge Base by Rebecca Jonas on 9/18/2018 12:25:49 PM

Symptoms

Tomcat fails with the following error in <APPIAN_HOME>/logs/tomcat-stdOut.log:

ERROR org.hibernate.connection.DatasourceConnectionProvider - Could not find datasource: jdbc/AppianDS
javax.naming.NameNotFoundException: Name [jdbc/AppianDS] is not bound in this Context. Unable to find [jdbc].

Cause

When the configure script is run, the content in tomcatResources.xml.<ENVIRONMENT> is copied to suite.xml in <APPIAN_HOME>\tomcat\apache-tomcat\conf\Catalina\localhost.

These errors occur if this content does not copy over correctly or if suite.xml is configured improperly.

Action

Ensure tomcatResources.xml.<ENVIRONMENT> is configured according to installation documentation and manually copy the entire contents of it to suite.xml in between the lines:


Restart Tomcat.

Affected Versions

This article applies to Appian 18.3 and later.

Last Reviewed: September 2018

Tags: Tomcat, application server, infrastructure

DRAFT KB-XXXX Tomcat fails with "BadPaddingException"

Jordan Horwat — Fri, 14 Sep 2018 17:25:42 GMT

Revision 12 posted to Appian Knowledge Base by Jordan Horwat on 9/14/2018 5:25:42 PM

Symptoms

Tomcat fails with one of the following errors in <APPIAN_HOME>/logs/tomcat-stdOut.log:

ERROR org.hibernate.connection.DatasourceConnectionProvider - Could not find datasource: jdbc/AppianDS
javax.naming.NameNotFoundException: Name [jdbc/AppianDS] is not bound in this Context. Unable to find [jdbc].

WARNING [localhost-startStop-1] org.apache.catalina.core.NamingContextListener.addResource Failed to register in JMX: [javax.naming.NamingException: Unexpected exception resolving reference [Root exception is javax.crypto.BadPaddingException: Given final block not properly padded]]
WARNING [localhost-startStop-1] org.apache.naming.NamingContext.lookup Unexpected exception resolving reference
javax.crypto.BadPaddingException: Given final block not properly padded.

Cause

When the configure script is run, the content in tomcatResources.xml.<ENVIRONMENT> is copied to suite.xml in <APPIAN_HOME>\tomcat\apache-tomcat\conf\Catalina\localhost.

These errors occur if this content does not copy over correctly or if suite.xml is configured improperly.

Action

Ensure tomcatResources.xml.<ENVIRONMENT> is configured according to installation documentation and manually copy the entire contents of it to suite.xml in between the lines:


Restart Tomcat.

Affected Versions

This article applies to Appian 18.3 and later.

Last Reviewed: September 2018

Tags: Tomcat, application server, infrastructure

DRAFT KB-XXXX Tomcat fails with "BadPaddingException"

Jordan Horwat — Fri, 14 Sep 2018 17:25:12 GMT

Revision 11 posted to Appian Knowledge Base by Jordan Horwat on 9/14/2018 5:25:12 PM

Symptoms

Tomcat fails with one of the following errors in <APPIAN_HOME>/logs/tomcat-stdOut.log:

ERROR org.hibernate.connection.DatasourceConnectionProvider - Could not find datasource: jdbc/AppianDS
javax.naming.NameNotFoundException: Name [jdbc/AppianDS] is not bound in this Context. Unable to find [jdbc].

WARNING [localhost-startStop-1] org.apache.catalina.core.NamingContextListener.addResource Failed to register in JMX: [javax.naming.NamingException: Unexpected exception resolving reference [Root exception is javax.crypto.BadPaddingException: Given final block not properly padded]]
WARNING [localhost-startStop-1] org.apache.naming.NamingContext.lookup Unexpected exception resolving reference
javax.crypto.BadPaddingException: Given final block not properly padded.

Cause

When the configure script is run, the content in tomcatResources.xml.<ENVIRONMENT> is copied to suite.xml in <APPIAN_HOME>\tomcat\apache-tomcat\conf\Catalina\localhost.

These errors occur if this content does not copy over correctly or if suite.xml is configured improperly.

Action

Ensure tomcatResources.xml.<ENVIRONMENT> is configured according to installation documentation and manually copy the entire contents of it to suite.xml in between the lines:


Restart Tomcat.

Affected Versions

This article applies to Appian 18.3.

Last Reviewed: September 2018

Tags: Tomcat, application server, infrastructure

DRAFT KB-XXXX Tomcat fails with "BadPaddingException"

Rebecca Jonas — Fri, 14 Sep 2018 17:14:54 GMT

Revision 10 posted to Appian Knowledge Base by Rebecca Jonas on 9/14/2018 5:14:54 PM

Symptoms

Tomcat fails with one of the following errors in <APPIAN_HOME>/logs/tomcat-stdOut.log:

ERROR org.hibernate.connection.DatasourceConnectionProvider - Could not find datasource: jdbc/AppianDS
javax.naming.NameNotFoundException: Name [jdbc/AppianDS] is not bound in this Context. Unable to find [jdbc].

WARNING [localhost-startStop-1] org.apache.catalina.core.NamingContextListener.addResource Failed to register in JMX: [javax.naming.NamingException: Unexpected exception resolving reference [Root exception is javax.crypto.BadPaddingException: Given final block not properly padded]]
WARNING [localhost-startStop-1] org.apache.naming.NamingContext.lookup Unexpected exception resolving reference
javax.crypto.BadPaddingException: Given final block not properly padded.

Cause

When the configure script is run, the content in tomcatResources.xml.<ENVIRONMENT> is copied to suite.xml in <APPIAN_HOME>\tomcat\apache-tomcat\conf\Catalina\localhost.

These errors occur if this content does not copy over correctly or if suite.xml is configured improperly.

Action

Ensure tomcatResources.xml.<ENVIRONMENT> is configured according to installation documentation and manually copy the entire contents of it to suite.xml in between the lines:



Restart Tomcat.

Affected Versions

This article applies to Appian 18.3.

Last Reviewed: September 2018

Tags: Tomcat, application server, infrastructure

DRAFT KB-XXXX Tomcat fails with "BadPaddingException"

Rebecca Jonas — Fri, 14 Sep 2018 15:20:08 GMT

Revision 1 posted to Appian Knowledge Base by Rebecca Jonas on 9/14/2018 3:20:08 PM

Symptoms

Tomcat fails with one of the following errors:

ERROR org.hibernate.connection.DatasourceConnectionProvider - Could not find datasource: jdbc/AppianDS

javax.naming.NameNotFoundException: Name [jdbc/AppianDS] is not bound in this Context. Unable to find [jdbc].

WARNING [localhost-startStop-1] org.apache.catalina.core.NamingContextListener.addResource Failed to register in JMX: [javax.naming.NamingException: Unexpected exception resolving reference [Root exception is javax.crypto.BadPaddingException: Given final block not properly padded]]

WARNING [localhost-startStop-1] org.apache.naming.NamingContext.lookup Unexpected exception resolving reference

javax.crypto.BadPaddingException: Given final block not properly padded.

Cause

When the configure script is run, the information in tomcatResources.xml.<ENVIRONMENT> is copied to suite.xml in <APPIAN_HOME>\tomcat\apache-tomcat\conf\Catalina\localhost

These errors occur if this code does not copy over correctly or if it is configured improperly.

Action

Manually copy the entire contents of tomcatResources.xml.<ENVIRONMENT> to suite.xml in between the lines and make sure it is configured according to installation documentation:

Tags: Tomcat, application server

DRAFT KB-XXXX Tomcat fails with "BadPaddingException"

Rebecca Jonas — Fri, 14 Sep 2018 12:32:20 GMT

Revision 9 posted to Appian Knowledge Base by Rebecca Jonas on 9/14/2018 12:32:20 PM

Symptoms

Tomcat fails with one of the following errors:

ERROR org.hibernate.connection.DatasourceConnectionProvider - Could not find datasource: jdbc/AppianDS
javax.naming.NameNotFoundException: Name [jdbc/AppianDS] is not bound in this Context. Unable to find [jdbc].

WARNING [localhost-startStop-1] org.apache.catalina.core.NamingContextListener.addResource Failed to register in JMX: [javax.naming.NamingException: Unexpected exception resolving reference [Root exception is javax.crypto.BadPaddingException: Given final block not properly padded]]
WARNING [localhost-startStop-1] org.apache.naming.NamingContext.lookup Unexpected exception resolving reference
javax.crypto.BadPaddingException: Given final block not properly padded.

Cause

When the configure script is run, the content in tomcatResources.xml.<ENVIRONMENT> is copied to suite.xml in <APPIAN_HOME>\tomcat\apache-tomcat\conf\Catalina\localhost

These errors occur if this content does not copy over correctly or if suite.xml is configured improperly.

Action

Make sure tomcatResources.xml.<ENVIRONMENT> is configured according to installation documentation and manually copy the entire contents of it to suite.xml in between the lines:



Restart Tomcat.

Tags: Tomcat, application server

DRAFT KB-XXXX Tomcat fails with "BadPaddingException"

Rebecca Jonas — Fri, 14 Sep 2018 12:28:48 GMT

Revision 8 posted to Appian Knowledge Base by Rebecca Jonas on 9/14/2018 12:28:48 PM

Symptoms

Tomcat fails with one of the following errors:

ERROR org.hibernate.connection.DatasourceConnectionProvider - Could not find datasource: jdbc/AppianDS
javax.naming.NameNotFoundException: Name [jdbc/AppianDS] is not bound in this Context. Unable to find [jdbc].

WARNING [localhost-startStop-1] org.apache.catalina.core.NamingContextListener.addResource Failed to register in JMX: [javax.naming.NamingException: Unexpected exception resolving reference [Root exception is javax.crypto.BadPaddingException: Given final block not properly padded]]
WARNING [localhost-startStop-1] org.apache.naming.NamingContext.lookup Unexpected exception resolving reference
javax.crypto.BadPaddingException: Given final block not properly padded.

Cause

When the configure script is run, the content in tomcatResources.xml.<ENVIRONMENT> is copied to suite.xml in <APPIAN_HOME>\tomcat\apache-tomcat\conf\Catalina\localhost

These errors occur if this content does not copy over correctly or if suite.xml is configured improperly.

Action

Make sure tomcatResources.xml.<ENVIRONMENT> is configured according to installation documentation and manually copy the entire contents of it to suite.xml in between the lines:

and restart Tomcat.

Tags: Tomcat, application server

DRAFT KB-XXXX Tomcat fails with "BadPaddingException"

Rebecca Jonas — Fri, 14 Sep 2018 12:25:17 GMT

Revision 7 posted to Appian Knowledge Base by Rebecca Jonas on 9/14/2018 12:25:17 PM

Symptoms

Tomcat fails with one of the following errors:

ERROR org.hibernate.connection.DatasourceConnectionProvider - Could not find datasource: jdbc/AppianDS
javax.naming.NameNotFoundException: Name [jdbc/AppianDS] is not bound in this Context. Unable to find [jdbc].

WARNING [localhost-startStop-1] org.apache.catalina.core.NamingContextListener.addResource Failed to register in JMX: [javax.naming.NamingException: Unexpected exception resolving reference [Root exception is javax.crypto.BadPaddingException: Given final block not properly padded]]
WARNING [localhost-startStop-1] org.apache.naming.NamingContext.lookup Unexpected exception resolving reference
javax.crypto.BadPaddingException: Given final block not properly padded.

Cause

When the configure script is run, the content in tomcatResources.xml.<ENVIRONMENT> is copied to suite.xml in <APPIAN_HOME>\tomcat\apache-tomcat\conf\Catalina\localhost

These errors occur if this content does not copy over correctly or if suite.xml is configured improperly.

Action

Make sure tomcatResources.xml.<ENVIRONMENT> is configured according to installation documentation and manually copy the entire contents of it to suite.xml in between the lines:

Tags: Tomcat, application server

DRAFT KB-XXXX Tomcat fails with "BadPaddingException"

Rebecca Jonas — Fri, 14 Sep 2018 12:22:47 GMT

Revision 6 posted to Appian Knowledge Base by Rebecca Jonas on 9/14/2018 12:22:47 PM

Symptoms

Tomcat fails with one of the following errors:

ERROR org.hibernate.connection.DatasourceConnectionProvider - Could not find datasource: jdbc/AppianDS
javax.naming.NameNotFoundException: Name [jdbc/AppianDS] is not bound in this Context. Unable to find [jdbc].

WARNING [localhost-startStop-1] org.apache.catalina.core.NamingContextListener.addResource Failed to register in JMX: [javax.naming.NamingException: Unexpected exception resolving reference [Root exception is javax.crypto.BadPaddingException: Given final block not properly padded]]
WARNING [localhost-startStop-1] org.apache.naming.NamingContext.lookup Unexpected exception resolving reference
javax.crypto.BadPaddingException: Given final block not properly padded.

Cause

When the configure script is run, the content in tomcatResources.xml.<ENVIRONMENT> is copied to suite.xml in <APPIAN_HOME>\tomcat\apache-tomcat\conf\Catalina\localhost

These errors occur if this code does not copy over correctly or if it is configured improperly.

Action

Make sure tomcatResources.xml.<ENVIRONMENT> is configured according to installation documentation and manually copy the entire contents of it to suite.xml in between the lines:

Tags: Tomcat, application server

DRAFT KB-XXXX Tomcat fails with "BadPaddingException"

Rebecca Jonas — Fri, 14 Sep 2018 12:14:52 GMT

Revision 5 posted to Appian Knowledge Base by Rebecca Jonas on 9/14/2018 12:14:52 PM

Symptoms

Tomcat fails with one of the following errors:

ERROR org.hibernate.connection.DatasourceConnectionProvider - Could not find datasource: jdbc/AppianDS
javax.naming.NameNotFoundException: Name [jdbc/AppianDS] is not bound in this Context. Unable to find [jdbc].

WARNING [localhost-startStop-1] org.apache.catalina.core.NamingContextListener.addResource Failed to register in JMX: [javax.naming.NamingException: Unexpected exception resolving reference [Root exception is javax.crypto.BadPaddingException: Given final block not properly padded]]

WARNING [localhost-startStop-1] org.apache.naming.NamingContext.lookup Unexpected exception resolving reference
javax.crypto.BadPaddingException: Given final block not properly padded.

Cause

When the configure script is run, the information in tomcatResources.xml.<ENVIRONMENT> is copied to suite.xml in <APPIAN_HOME>\tomcat\apache-tomcat\conf\Catalina\localhost

These errors occur if this code does not copy over correctly or if it is configured improperly.

Action

Make sure tomcatResources.xml.<ENVIRONMENT> is configured according to installation documentation and manually copy the entire contents of it to suite.xml in between the lines:

Tags: Tomcat, application server

DRAFT KB-XXXX Tomcat fails with "BadPaddingException"

Rebecca Jonas — Fri, 14 Sep 2018 12:14:37 GMT

Revision 4 posted to Appian Knowledge Base by Rebecca Jonas on 9/14/2018 12:14:37 PM

Symptoms

Tomcat fails with one of the following errors:

ERROR org.hibernate.connection.DatasourceConnectionProvider - Could not find datasource: jdbc/AppianDS

javax.naming.NameNotFoundException: Name [jdbc/AppianDS] is not bound in this Context. Unable to find [jdbc].

WARNING [localhost-startStop-1] org.apache.catalina.core.NamingContextListener.addResource Failed to register in JMX: [javax.naming.NamingException: Unexpected exception resolving reference [Root exception is javax.crypto.BadPaddingException: Given final block not properly padded]]

WARNING [localhost-startStop-1] org.apache.naming.NamingContext.lookup Unexpected exception resolving reference
javax.crypto.BadPaddingException: Given final block not properly padded.

Cause

When the configure script is run, the information in tomcatResources.xml.<ENVIRONMENT> is copied to suite.xml in <APPIAN_HOME>\tomcat\apache-tomcat\conf\Catalina\localhost

These errors occur if this code does not copy over correctly or if it is configured improperly.

Action

Make sure tomcatResources.xml.<ENVIRONMENT> is configured according to installation documentation and manually copy the entire contents of it to suite.xml in between the lines:

Tags: Tomcat, application server

DRAFT KB-XXXX Tomcat fails with "BadPaddingException"

Rebecca Jonas — Fri, 14 Sep 2018 12:14:23 GMT

Revision 3 posted to Appian Knowledge Base by Rebecca Jonas on 9/14/2018 12:14:23 PM

Symptoms

Tomcat fails with one of the following errors:

ERROR org.hibernate.connection.DatasourceConnectionProvider - Could not find datasource: jdbc/AppianDS

javax.naming.NameNotFoundException: Name [jdbc/AppianDS] is not bound in this Context. Unable to find [jdbc].

WARNING [localhost-startStop-1] org.apache.catalina.core.NamingContextListener.addResource Failed to register in JMX: [javax.naming.NamingException: Unexpected exception resolving reference [Root exception is javax.crypto.BadPaddingException: Given final block not properly padded]]

WARNING [localhost-startStop-1] org.apache.naming.NamingContext.lookup Unexpected exception resolving reference

 javax.crypto.BadPaddingException: Given final block not properly padded.

Cause

When the configure script is run, the information in tomcatResources.xml.<ENVIRONMENT> is copied to suite.xml in <APPIAN_HOME>\tomcat\apache-tomcat\conf\Catalina\localhost

These errors occur if this code does not copy over correctly or if it is configured improperly.

Action

Make sure tomcatResources.xml.<ENVIRONMENT> is configured according to installation documentation and manually copy the entire contents of it to suite.xml in between the lines:

Tags: Tomcat, application server

DRAFT KB-XXXX Tomcat fails with "BadPaddingException"

Rebecca Jonas — Fri, 14 Sep 2018 11:22:07 GMT

Revision 2 posted to Appian Knowledge Base by Rebecca Jonas on 9/14/2018 11:22:07 AM

Symptoms

Tomcat fails with one of the following errors:

ERROR org.hibernate.connection.DatasourceConnectionProvider - Could not find datasource: jdbc/AppianDS

javax.naming.NameNotFoundException: Name [jdbc/AppianDS] is not bound in this Context. Unable to find [jdbc].

WARNING [localhost-startStop-1] org.apache.catalina.core.NamingContextListener.addResource Failed to register in JMX: [javax.naming.NamingException: Unexpected exception resolving reference [Root exception is javax.crypto.BadPaddingException: Given final block not properly padded]]

WARNING [localhost-startStop-1] org.apache.naming.NamingContext.lookup Unexpected exception resolving reference

javax.crypto.BadPaddingException: Given final block not properly padded.

Cause

When the configure script is run, the information in tomcatResources.xml.<ENVIRONMENT> is copied to suite.xml in <APPIAN_HOME>\tomcat\apache-tomcat\conf\Catalina\localhost

These errors occur if this code does not copy over correctly or if it is configured improperly.

Action

Make sure tomcatResources.xml.<ENVIRONMENT> is configured according to installation documentation and manually copy the entire contents of it to suite.xml in between the lines:

Tags: Tomcat, application server