CF2021 scheduler errors

[rspitzmd]

Hello community,

on our new server with CF2021 (Upd. 3), there are regular errors appearing in the exception.log with the following content:

"Error","scheduler-2","03/01/22","10:17:21","","The cause of this output exception was that: coldfusion.tagext.sql.QueryParamTag$InvalidDataException: Invalid data value VERTEILER2_PROD_16409_c752c3705ca7899c-AF13A205-D150-F002-4AE23F50F4561FE2 exceeds maxlength setting 40.. The specific sequence of files included or processed is: '', line: 115 "

The application "VERTEILER2_PROD" has long-running sessions which are kept alive by regular "pings" sent via javascript from the client's browser, even when there is no user interaction. Don't ask, this is a non-negotiable requirement by some high-level users and has not caused any trouble so far. Apart from the above entries in the exception.log, I haven't had any user feedback about problems. The application itself was migrated without any code changes from the previous CF2016 instance to the new one with CF2021, but in the CF2021 server settings, we enabled the "Use UUID for cftoken" option.

We have no application level scheduled tasks configured, and the only server level scheduled task is the regular check for CF updates. I assume that the "scheduler-*" threads are internal threads that do not run user code, so as long as there are no application errors reported by users, should I just ignore this issue? 

Regards, Richard

[BKBK · Accepted solution]

That exception usually occurs when the data value exceeds the "maxlength". Locate in your code the following attribute:

maxLength="40"

Increase its value to, say, 100, to ensure the field will accommodate strings such as 'VERTEILER2_PROD_16409_c752c3705ca7899c-AF13A205-D150-F002-4AE23F50F4561FE2'

[rspitzmd]

Hi BKBK,

thanks for pointing me in the right direction. I was well aware of the "maxlength" property in a <cfqueryparam> Tag and had ruled out that 'maxLength="40"' occured anywhere in the relevant .cfm files, but had overlooked that there was one such occurence in the "onSessionEnd" function of Application.cfc. DUH!

Regards, Richard

[BKBK]

Happens to all of us. 🙂