Cfthread not working (New upgrade to CF 2018 std)

Now it get weirder. I was able to make it work if I use a cfinclude inside the cfthread like this:

thrpage.cfm

=============================================

<cfthread action="run" name="THR1">

    <cfinclude template="action.cfm">

</cfthread>

=============================================

action.cfm

=============================================

<cfquery name="QR1" datasource="mydsn" dbtype="ODBC">

INSERT INTO TBL1 (field1) VALUES ('ok')

</cfquery>

=============================================

But that only works if I first call the stand alone page "action.cfm" before any subsequent calls to "thrpage.cfm". This will continue to work until I edit the "action.cfm" page. As soon as I edit that page the cfthread stops working. Any edit like adding a space or character to the end of the page will not allow subsequent chthreads on the "thrpage.cfm" until I re-execute the "action.cfm" on the browser.

I suspect this could be a cache issue. But even restarting the server will not make it work. Only calling the "action.cfm" page first seams to solve the issue; unless that page is edited.

More info about this issue... It's apparently an issue with MySQL 8 support. If I setup the same DSN w/ MySQL 5.7 instead of MySQL 8.0 the cfthread works as expected.

I can connect and execute DB Commands (like Inserts/updates) on MySQL 8 using the mysql-connector-java-8.0.12.jar. This works flawlessly on any .CFM page; even with a query inside a cfinclude. But as soon as I place the cfquery inside a cfthread tag nothing happens I get the log error on the OP.

The same example as above but using a DSN on MySQL 5.7 works without issues.

Can anyone with CF2018 & MySQL8.0 confirm?

If you're inserting into the same table within the CFTHREAD that you're inserting into before and after, I'm not surprised that you're having problems. Databases usually require some way to handle transactions so that they don't mess up other transactions. In some databases, this is handled by locking. So, the first query would place an exclusive lock on the table, the second query would run in a second thread (concurrently, not serially) and the third query would again require an exclusive lock on the same table. In a single program, this is usually not a problem because the queries would be handled serially. There are all kinds of potential complications here, as well: what is the transaction isolation level, etc, etc.

Dave Watts, Fig Leaf Software

Could you show us the code you used. I strongly suspect it needs to be corrected.

I tested the following code on a database table named tbl (having 2 columns, of type date and UUID):

<cfset sql1="INSERT INTO tbl VALUES(#now()#,'#createuuid()#')">

<cfset queryExecute(sql1, {}, {datasource="myDSN"})>

<cfthread action="RUN" name="Test_Thread">

   <cfset sql2="INSERT INTO tbl VALUES(#dateAdd('d',1,now())#,'#createuuid()#')">

   <cfset queryExecute(sql2, {}, {datasource="myDSN"})>

</cfthread>

<cfset sql3="INSERT INTO tbl VALUES(#dateAdd('d',2,now())#,'#createuuid()#')">

<cfset queryExecute(sql3, {}, {datasource="myDSN"})>

It works as expected. Nevertheless, sometimes the insert in the thread is done last. But, then again, that is what you would expect of asynchronous threads.