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

Parmida Borhani — Wed, 01 May 2019 04:28:50 GMT

Current Revision posted to Appian Knowledge Base by Parmida Borhani on 5/1/2019 4:28:50 AM

Symptoms

After upgrading an environment to Appian version 18.4 or later, the following warning appears in the application server log:

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=<NAME OF THE IMPACTED PROCESS MODEL>, id=<ID OF THE IMPACTED PROCESS MODEL>]

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 no longer necessary.

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 stored procedure to run. This warning can be safely ignored.

To avoid seeing it, 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: April 2019

Tags: known issues, database, application design, open issues

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

Diaba Konate — Tue, 30 Apr 2019 15:41:47 GMT

Revision 6 posted to Appian Knowledge Base by Diaba Konate on 4/30/2019 3:41:47 PM

Symptoms

After upgrading an environment to Appian version 18.4 or later, the following warning appears in the application server log:

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=<NAME OF THE IMPACTED PROCESS MODEL>, id=<ID OF THE IMPACTED PROCESS MODEL>]

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 no longer necessary.

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 stored procedure to run. This warning can be safely ignored.

To avoid seeing it, 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: April 2019

Tags: known issues, database, application design, open issues

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

Diaba Konate — Tue, 30 Apr 2019 15:39:12 GMT

Revision 5 posted to Appian Knowledge Base by Diaba Konate on 4/30/2019 3:39:12 PM

Symptoms

After upgrading an environment to Appian version 18.4 or later, the following warning appears in the application server log:

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=<NAME OF THE IMPACTED PROCESS MODEL>, id=<ID OF THE IMPACTED PROCESS MODEL>]

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 no longer necessary.

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 stored procedure to run. This warning can be safely ignored.

To avoid seeing it, 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

Tags: known issues, database, application design, open issues

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

Diaba Konate — Thu, 14 Mar 2019 09:40:03 GMT

Revision 4 posted to Appian Knowledge Base by Diaba Konate on 3/14/2019 9:40:03 AM

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=<NAME OF THE IMPACTED PROCESS MODEL>, 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 it, 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

Tags: known issues, database, application design, open issues

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

Diaba Konate — Wed, 13 Mar 2019 16:55:10 GMT

Revision 1 posted to Appian Knowledge Base by Diaba Konate on 3/13/2019 4:55:10 PM

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

Tags: known issues, database, application design, open issues

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

Diaba Konate — Wed, 13 Mar 2019 12:57:32 GMT

Revision 3 posted to Appian Knowledge Base by Diaba Konate on 3/13/2019 12:57:32 PM

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=<NAME OF THE IMPACTED PROCESS MODEL>, 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 IT, 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

Tags: known issues, database, application design, open issues

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

Diaba Konate — Wed, 13 Mar 2019 12:56:36 GMT

Revision 2 posted to Appian Knowledge Base by Diaba Konate on 3/13/2019 12:56:36 PM

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=<NAME OF THE IMPACTED PROCESS MODEL>, 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

Tags: known issues, database, application design, open issues