KB-1242 "Unable to convert to expected Date/Time Java types" error repeated in application server log

Jordan Horwat — Mon, 23 Jul 2018 17:36:39 GMT

Current Revision posted to Appian Knowledge Base by Jordan Horwat on 7/23/2018 5:36:39 PM

Symptoms

The following error is repeated in the application server log:

ERROR com.appiancorp.process.runtime.activities.QueryRdbmsActivity - Unable to convert to expected Date/Time Java types
java.lang.NullPointerException

There is no error on the front end.

Cause

This will happen if Appian pulls back a date/datetime column from a database and one of the values in that column is null.

Action

This error can be ignored. This has been reported to the Appian product team as AN-45088 to improve the exception handling.

To determine what table is causing the problem, follow the steps below:

Navigate to <APPIAN_HOME>/ear/suite.ear/resources
Search for the following line in the appian_log4j.properties and change the logging level to DEBUG as follows:

log4j.logger.com.appiancorp.process.runtime.activities.QueryRdbmsActivity=DEBUG

This will print DEBUG lines in the application server log and the output will show what query is causing this problem. You can then decide from there whether you should add a default value to that field which is null.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: March 2017

Tags: known issues, application server, infrastructure, open issues