You are currently reviewing an older revision of this page.

DRAFT KB-XXXX Invalid JNDI name warning message appears after upgrade to 18.4

Symptoms

Following the upgrade of an environment to Appian version 18.4 and later, this warning appears in the application server log:

2019-01-08 05:52:04,412 [Appian Work Item - 414208 - execution00 : UnattendedJavaActivityRequest] WARN  com.appiancorp.process.runtime.activities.QueryRdbmsActivity - Detected attempt to lookup datasource connection using invalid JNDI name [java:/jdbc/Appian]; attempting to recover by looking up datasource using [jdbc/Appian]. Update the datasource configuration in the Query Database nodes in the following model to avoid this warning for new process instances of the model [name=ADMIN_EAGLE_DEBUG SUIVI DES RETARDS, id=10638]

Cause

The above warning is printed when the input of an execute stored procedure call includes this prefix: java:/. Since Appian version 18.4, this prefix is not needed anymore.

A request to suppress this warning has been logged to the Appian product team as AN-115248.

Action

This issue does not negatively impact Appian, nor does it prevent the store procedure to run. This warning can be safely ignored.

To avoid seeing this warning, modify the input of the execute stored procedure to remove the java:/ prefix.

Affected Versions

This article applies to Appian 18.4 and later.

Last Reviewed: March 2019