KB-1762 Plugin fails after upgrade to 18.3 with "Unable to find [jdbc]" error in application server log

Jordan Horwat — Fri, 26 Oct 2018 20:43:05 GMT

Current Revision posted to Appian Knowledge Base by Jordan Horwat on 10/26/2018 8:43:05 PM

Symptoms

A plugin that was previously working fails after an upgrade to Appian 18.3, and the following error appears in the Tomcat log:

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

Cause

The plugin is configured to connect to the database using a format that is no longer accepted by Tomcat. For example:

DATASOURCE_CONTEXT=java:/jdbc/Appian

Tomcat does not accept the java:/ prefix in datasource context property.

Action

Unzip the plugin JAR file.
Search the unzipped plugin files for the problematic datasource context string, java:/jdbc/<DB_Name>. This is often defined in a properties file and referenced in the Java source code.
Remove the java:/ prefix from the property. This change can be made from within archival software, so the JAR does not have to be rebuilt.
Redeploy the plugin.

Affected Versions

This article applies to Appian 18.3 and later.

Last Reviewed: October 2018

Tags: database, plug-ins, infrastructure, plugins

KB-1762 Plugin fails after upgrade to 18.3 with "Unable to find [jdbc]" error in application server log

Jordan Horwat — Fri, 26 Oct 2018 16:42:42 GMT

Revision 20 posted to Appian Knowledge Base by Jordan Horwat on 10/26/2018 4:42:42 PM

Symptoms

A plugin that was previously working fails after an upgrade to Appian 18.3, and the following error appears in the Tomcat log:

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

Cause

The plugin is configured to connect to the database using a format that is no longer accepted by Tomcat. For example:

DATASOURCE_CONTEXT=java:/jdbc/Appian

Tomcat does not accept the java:/ prefix in datasource context property.

Action

Unzip the plugin JAR file.
Search the unzipped plugin files for the problematic datasource context string, "java:/jdbc/<DB_Name>". This is often defined in a properties file and referenced in the Java source code.
Remove the java:/ prefix from the property. This change can be made from within archival software, so the JAR does not have to be rebuilt.
Redeploy the plugin.

Affected Versions

This article applies to Appian 18.3 and later.

Last Reviewed: October 2018

Tags: database, shared components, infrastructure, plugins

DRAFT KB-XXXX Plugin fails after upgrade to 18.3 with "Unable to find [jdbc]" error in application server log

Daniel DeVeau — Fri, 26 Oct 2018 14:22:27 GMT

Revision 19 posted to Appian Knowledge Base by Daniel DeVeau on 10/26/2018 2:22:27 PM

Symptoms

A plugin that was previously working fails after an upgrade to Appian 18.3, and the following error appears in the Tomcat log:

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

Cause

The plugin is configured to connect to the database using a format that is no longer accepted by Tomcat. For example:

DATASOURCE_CONTEXT=java:/jdbc/Appian

Tomcat does not accept the 'java:' prefix in datasource context property.

Action

Unzip the plugin JAR file.
Search the unzipped plugin files for the problematic datasource context string, "java:/jdbc/<DB_Name>". This is often defined in a properties file and referenced in the Java source code.
Remove the "java:/" prefix from the property. This change can be made from within archival software, so the JAR does not have to be rebuilt.
Redeploy the plugin.

Affected Versions

This article applies to Appian 18.3 and later.

Last Reviewed: October 2018

Tags: database, shared components, infrastructure, plugins

DRAFT KB-XXXX Plugin fails after upgrade to 18.3 with "Unable to find [jdbc]" error in application server log

Daniel DeVeau — Fri, 26 Oct 2018 14:22:01 GMT

Revision 18 posted to Appian Knowledge Base by Daniel DeVeau on 10/26/2018 2:22:01 PM

Symptoms

A plugin that was previously working fails after an upgrade to Appian 18.3, and the following error appears in the Tomcat log:

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

Cause

The plugin is configured to connect to the database using a format that is no longer accepted by Tomcat. For example:

DATASOURCE_CONTEXT=java:/jdbc/Appian

Tomcat does not accept the 'java:' prefix in datasource context property.

Action

Unzip the plugin JAR file.
Search the unzipped plugin files for the problematic datasource context string, "java:/jdbc/<DB_Name>". This is often defined in a properties file and referenced in the Java source code.
Remove the "java:/" prefix. This change can be made from within archival software, so the JAR does not have to be rebuilt.
Redeploy the plugin.

Affected Versions

This article applies to Appian 18.3 and later.

Last Reviewed: October 2018

Tags: database, shared components, infrastructure, plugins

DRAFT KB-XXXX Plugin fails after upgrade to 18.3 with "Unable to find [jdbc]" error in application server log

Daniel DeVeau — Fri, 26 Oct 2018 14:21:12 GMT

Revision 17 posted to Appian Knowledge Base by Daniel DeVeau on 10/26/2018 2:21:12 PM

Symptoms

A plugin that was previously working fails after an upgrade to Appian 18.3, and the following error appears in the Tomcat log:

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

Cause

The plugin is configured to connect to the database using a format that is no longer accepted by Tomcat. For example:

DATASOURCE_CONTEXT=java:/jdbc/Appian

Tomcat does not accept the 'java:' prefix in datasource context property.

Action

Unzip the plugin JAR file.
Search the unzipped plugin files for the problematic datasource context string 'java:/jdbc/<DB_Name>'. This is often defined in a properties file and referenced in the Java source code.
Remove the 'java:/' prefix. This change can be made from within archival software, so the JAR does not have to be rebuilt.
Redeploy the plugin.

Affected Versions

This article applies to Appian 18.3 and later.

Last Reviewed: October 2018

Tags: database, shared components, infrastructure, plugins

DRAFT KB-XXXX Plugin fails after upgrade to 18.3 with "Unable to find [jdbc]" error in application server log

Daniel DeVeau — Fri, 26 Oct 2018 14:20:20 GMT

Revision 16 posted to Appian Knowledge Base by Daniel DeVeau on 10/26/2018 2:20:20 PM

Symptoms

A plugin that was previously working fails after an upgrade to Appian 18.3, and the following error appears in the Tomcat log:

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

Cause

The plugin is configured to connect to the database using a format that is no longer accepted by Tomcat. For example:

DATASOURCE_CONTEXT=java:/jdbc/Appian

Tomcat does not accept the 'java:' prefix in datasource context property.

Action

Unzip the plugin JAR file.
Identify where the datasource context is defined within the plugin by searching the plugin files for the problematic context string 'java:/jdbc/<DB_Name>'. This is often defined in a properties file and referenced in the Java source code.
Remove the 'java:/' prefix. This change can be made from within archival software, so the JAR does not have to be rebuilt.
Redeploy the plugin.

Affected Versions

This article applies to Appian 18.3 and later.

Last Reviewed: October 2018

Tags: database, shared components, infrastructure, plugins

DRAFT KB-XXXX Plugin fails after upgrade to 18.3 with "Unable to find [jdbc]" error in application server log

Daniel DeVeau — Fri, 26 Oct 2018 14:15:23 GMT

Revision 15 posted to Appian Knowledge Base by Daniel DeVeau on 10/26/2018 2:15:23 PM

Symptoms

A plugin that was previously working fails after an upgrade to Appian 18.3, and the following error appears in the Tomcat log:

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

Cause

The plugin is configured to connect to the database using a format that is no longer accepted by Tomcat. For example:

DATASOURCE_CONTEXT=java:/jdbc/Appian

Tomcat does not accept the 'java:' prefix in datasource context property.

Action

Unzip the plugin JAR file.
Identify where the datasource context is defined within the plugin by searching the plugin files for the problematic context string 'java:/jdbc/<DB_Name>'. This is often defined in a properties file.
Remove the 'java:/' prefix. This change can be made from within archival software, so the JAR does not have to be rebuilt.
Redeploy the plugin.

Affected Versions

This article applies to Appian 18.3 and later.

Last Reviewed: October 2018

Tags: database, shared components, infrastructure, plugins

DRAFT KB-XXXX Plugin fails after upgrade to 18.3 with "Unable to find [jdbc]" error in application server log

Daniel DeVeau — Fri, 26 Oct 2018 14:15:00 GMT

Revision 14 posted to Appian Knowledge Base by Daniel DeVeau on 10/26/2018 2:15:00 PM

Symptoms

A plugin that was previously working fails after an upgrade to Appian 18.3, and the following error appears in the Tomcat log:

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

Cause

The plugin is configured to connect to the database using a format that is no longer accepted by Tomcat. For example:

DATASOURCE_CONTEXT=java:/jdbc/Appian

Tomcat does not accept the 'java:' prefix in datasource context property.

Action

Unzip the plugin JAR file.
Identify where the datasource context is defined within the plugin by searching the plugin files for the problematic context string: "java:/jdbc/<DB_Name>". This is often defined in a properties file.
Remove the 'java:/' prefix. This change can be made from within archival software, so the JAR does not have to be rebuilt.
Redeploy the plugin.

Affected Versions

This article applies to Appian 18.3 and later.

Last Reviewed: October 2018

Tags: database, shared components, infrastructure, plugins

DRAFT KB-XXXX Plugin fails after upgrade to 18.3 with "Unable to find [jdbc]" error in application server log

Daniel DeVeau — Fri, 26 Oct 2018 14:14:34 GMT

Revision 13 posted to Appian Knowledge Base by Daniel DeVeau on 10/26/2018 2:14:34 PM

Symptoms

A plugin that was previously working fails after an upgrade to Appian 18.3, and the following error appears in the Tomcat log:

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

Cause

The plugin is configured to connect to the database using a format that is no longer accepted by Tomcat. For example:

DATASOURCE_CONTEXT=java:/jdbc/Appian

Tomcat does not accept the 'java:' prefix in datasource context property.

Action

Unzip the plugin JAR file.
Identify where the datasource context is defined within the plugin by searching the plugin files for the context string: "java:/jdbc/<DB_Name>". This is often defined in a properties file.
Remove the 'java:/' prefix. This change can be made from within archival software, so the JAR does not have to be rebuilt.
Redeploy the plugin.

Affected Versions

This article applies to Appian 18.3 and later.

Last Reviewed: October 2018

Tags: database, shared components, infrastructure, plugins

DRAFT KB-XXXX Plugin fails after upgrade to 18.3 with "Unable to find [jdbc]" error in application server log

Daniel DeVeau — Fri, 26 Oct 2018 14:12:01 GMT

Revision 12 posted to Appian Knowledge Base by Daniel DeVeau on 10/26/2018 2:12:01 PM

Symptoms

A plugin that was previously working fails after an upgrade to Appian 18.3, and the following error appears in the Tomcat log:

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

Cause

The plugin is configured to connect to the database using a format that is no longer accepted by Tomcat. For example:

DATASOURCE_CONTEXT=java:/jdbc/Appian

Tomcat does not accept the 'java:' prefix in datasource context property.

Action

Unzip the plugin JAR file.
Identify where the datasource context is defined within the plugin by searching the plugin files for the context string: "java:/jdbc/<DB_Name>". This is often defined in a properties file.
Remove the 'java:/' prefix. This change can be made from within archival software
Redeploy the plugin.

Affected Versions

This article applies to Appian 18.3 and later.

Last Reviewed: October 2018

Tags: database, shared components, infrastructure, plugins

DRAFT KB-XXXX Plugin fails after upgrade to 18.3 with "Unable to find [jdbc]" error in application server log

Daniel DeVeau — Fri, 26 Oct 2018 14:11:51 GMT

Revision 11 posted to Appian Knowledge Base by Daniel DeVeau on 10/26/2018 2:11:51 PM

Symptoms

A plugin that was previously working fails after an upgrade to Appian 18.3, and the following error appears in the Tomcat log:

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

Cause

The plugin is configured to connect to the database using a format that is no longer accepted by Tomcat. For example:

DATASOURCE_CONTEXT=java:/jdbc/Appian

Tomcat does not accept the 'java:' prefix in datasource context property.

Action

Unzip the plugin JAR file.
Identify where the datasource context is defined within the plugin by searching the plugin files for the context string "java:/jdbc/<DB_Name>". This is often defined in a properties file.
Remove the 'java:/' prefix. This change can be made from within archival software
Redeploy the plugin.

Affected Versions

This article applies to Appian 18.3 and later.

Last Reviewed: October 2018

Tags: database, shared components, infrastructure, plugins

KB-XXXX Plugin fails after upgrade to 18.3 with error in app server log, "Unable to find [jdbc]"

Daniel DeVeau — Thu, 25 Oct 2018 20:01:00 GMT

Revision 1 posted to Appian Knowledge Base by Daniel DeVeau on 10/25/2018 8:01:00 PM

Symptoms

A plugin stops working after an upgrade to 18.3, and the following error appears in the Tomcat logs:

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

Cause

The plugin is trying to connect to the database using a format that is no longer accepted by Tomcat. For example:

DATASOURCE_CONTEXT=java:/jdbc/Appian

Tomcat does not accept the 'java:' prefix in datasource contexts.

Tomcate does not accept the 'java:' prefix in datasource contexts.

Action

Affected Versions

This article applies to Appian 18.3 and later.

DRAFT KB-XXXX Plugin fails after upgrade to 18.3 with "Unable to find [jdbc]" error in application server log

Jordan Horwat — Thu, 25 Oct 2018 16:48:37 GMT

Revision 10 posted to Appian Knowledge Base by Jordan Horwat on 10/25/2018 4:48:37 PM

Symptoms

A plugin that was previously working fails after an upgrade to Appian 18.3, and the following error appears in the Tomcat log:

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

Cause

The plugin is configured to connect to the database using a format that is no longer accepted by Tomcat. For example:

DATASOURCE_CONTEXT=java:/jdbc/Appian

Tomcat does not accept the 'java:' prefix in datasource context property.

Action

Identify where the datasource context is defined within the plugin. This is often defined in a properties file.
Remove the 'java:/' prefix.
Redeploy the plugin.

Affected Versions

This article applies to Appian 18.3 and later.

Last Reviewed: October 2018

Tags: database, shared components, infrastructure, plugins

KB-XXXX Plugin fails after upgrade to 18.3 with "Unable to find [jdbc]" error in app server log

Daniel DeVeau — Thu, 25 Oct 2018 16:31:42 GMT

Revision 9 posted to Appian Knowledge Base by Daniel DeVeau on 10/25/2018 4:31:42 PM

Symptoms

A plugin stops working after an upgrade to 18.3, and the following error appears in the Tomcat logs:

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

Cause

The plugin is trying to connect to the database using a format that is no longer accepted by Tomcat. For example:

DATASOURCE_CONTEXT=java:/jdbc/Appian

Tomcat does not accept the 'java:' prefix in datasource contexts.

Action

1. Identify where the datasource context is defined in the plugin. This is often defined in a properties file.

2. remove the 'java:/' prefix

3. Redeploy the plugin.

Affected Versions

This article applies to Appian 18.3 and later.

Tags: database, infrastructure, plugins

KB-XXXX Plugin fails after upgrade to 18.3 with error in app server log, "Unable to find [jdbc]"

Daniel DeVeau — Thu, 25 Oct 2018 16:27:40 GMT

Revision 8 posted to Appian Knowledge Base by Daniel DeVeau on 10/25/2018 4:27:40 PM

Symptoms

A plugin stops working after an upgrade to 18.3, and the following error appears in the Tomcat logs:

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

Cause

The plugin is trying to connect to the database using a format that is no longer accepted by Tomcat. For example:

DATASOURCE_CONTEXT=java:/jdbc/Appian

Tomcat does not accept the 'java:' prefix in datasource contexts.

Action

1. Identify where the datasource context is defined in the plugin. This is often defined in a properties file.

2. remove the 'java:/' prefix

3. Redeploy the plugin.

Affected Versions

This article applies to Appian 18.3 and later.

Tags: database, infrastructure, plugins

KB-XXXX Plugin fails after upgrade to 18.3 with error in app server log, "Unable to find [jdbc]"

Daniel DeVeau — Thu, 25 Oct 2018 16:25:37 GMT

Revision 7 posted to Appian Knowledge Base by Daniel DeVeau on 10/25/2018 4:25:37 PM

Symptoms

A plugin stops working after an upgrade to 18.3, and the following error appears in the Tomcat logs:

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

Cause

The plugin is trying to connect to the database using a format that is no longer accepted by Tomcat. For example:

DATASOURCE_CONTEXT=java:/jdbc/Appian

Tomcat does not accept the 'java:' prefix in datasource contexts.

Action

Identify where the datasource context is defined in the plugin, remove the 'java:' prefix, and redeploy the plugin.

Affected Versions

This article applies to Appian 18.3 and later.

Tags: database, infrastructure, plugins

KB-XXXX Plugin fails after upgrade to 18.3 with error in app server log, "Unable to find [jdbc]"

Daniel DeVeau — Thu, 25 Oct 2018 16:16:01 GMT

Revision 6 posted to Appian Knowledge Base by Daniel DeVeau on 10/25/2018 4:16:01 PM

Symptoms

A plugin stops working after an upgrade to 18.3, and the following error appears in the Tomcat logs:

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

Cause

The plugin is trying to connect to the database using a format that is no longer accepted by Tomcat. For example:

DATASOURCE_CONTEXT=java:/jdbc/Appian

Tomcat does not accept the 'java:' prefix in datasource contexts.

Action

Identify where the datasource context is defined in the plugin, remove the 'java:' prefix, and redeploy the plugin.

Affected Versions

This article applies to Appian 18.3 and later.

KB-XXXX Plugin fails after upgrade to 18.3 with error in app server log, "Unable to find [jdbc]"

Daniel DeVeau — Thu, 25 Oct 2018 16:14:13 GMT

Revision 5 posted to Appian Knowledge Base by Daniel DeVeau on 10/25/2018 4:14:13 PM

Symptoms

A plugin stops working after an upgrade to 18.3, and the following error appears in the Tomcat logs: Tomcat does not accept the 'java:' prefix in datasource context

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

Cause

The plugin is trying to connect to the database using a format that is no longer accepted by Tomcat. For example:

DATASOURCE_CONTEXT=java:/jdbc/Appian

Tomcat does not accept the 'java:' prefix in datasource contexts.

Action

Identify where the datasource context is defined in the plugin, remove the 'java:' prefix, and redeploy the plugin.

Affected Versions

This article applies to Appian 18.3 and later.

KB-XXXX Plugin fails after upgrade to 18.3 with error in app server log, "Unable to find [jdbc]"

Daniel DeVeau — Thu, 25 Oct 2018 16:06:55 GMT

Revision 4 posted to Appian Knowledge Base by Daniel DeVeau on 10/25/2018 4:06:55 PM

Symptoms

A plugin stops working after an upgrade to 18.3, and the following error appears in the Tomcat logs: Tomcat does not accept the 'java:' prefix in datasource context

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

Cause

The plugin is trying to connect to the database using a format that is no longer accepted by Tomcat. For example:

DATASOURCE_CONTEXT=java:/jdbc/Appian

Tomcat does not accept the 'java:' prefix in datasource contexts.

Action

Affected Versions

This article applies to Appian 18.3 and later.

KB-XXXX Plugin fails after upgrade to 18.3 with error in app server log, "Unable to find [jdbc]"

Daniel DeVeau — Thu, 25 Oct 2018 16:05:49 GMT

Revision 3 posted to Appian Knowledge Base by Daniel DeVeau on 10/25/2018 4:05:49 PM

Symptoms

A plugin stops working after an upgrade to 18.3, and the following error appears in the Tomcat logs: Tomcat does not accept the 'java:' prefix in datasource context

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

Cause

The plugin is trying to connect to the database using a format that is no longer accepted by Tomcat. For example:

DATASOURCE_CONTEXT=java:/jdbc/Appian

Action

Tomcat does not accept the 'java:' prefix in datasource contexts.

Affected Versions

This article applies to Appian 18.3 and later.

KB-XXXX Plugin fails after upgrade to 18.3 with error in app server log, "Unable to find [jdbc]"

Daniel DeVeau — Thu, 25 Oct 2018 16:04:13 GMT

Revision 2 posted to Appian Knowledge Base by Daniel DeVeau on 10/25/2018 4:04:13 PM

Symptoms

A plugin stops working after an upgrade to 18.3, and the following error appears in the Tomcat logs:

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

Cause

The plugin is trying to connect to the database using a format that is no longer accepted by Tomcat. For example:

DATASOURCE_CONTEXT=java:/jdbc/Appian

Action

Affected Versions

This article applies to Appian 18.3 and later.