TL/DR:

_
Lucee re-uses closed task ID numbers after a restart, and it shouldn’t. Delete all tasks (on the admin’s “Services - Tasks” page). Restart Lucee. Make a task, cause it to become closed. Restart Lucee. Make another task. Both have ID = 1. Click detail for either, you see detail for both. NOT GOOD, needs fix._

FULL TEXT:

It seems there’s a bug with task threads. Here’s how to reproduce it:

1. Make sure there are no task threads (delete all if needed).
2. Shutdown Lucee.
3. Start Lucee.

These three steps appear to ensure that when we create a task thread, it’ll have ID = 1.

4. Create a task thread that always fails (contains just a CFTHROW for example). It will be given ID = 1.
5. Repeatedly execute it (either manually or just wait for all its retries to happen) until it’s “closed” and appears in red in the adminstrator “Services - Tasks” page.
6. Shutdown Lucee.

Here’s the fun part:

7. Start Lucee.
8. Go into the “Services - Tasks” admin page, note the closed ID = 1 red task is still there.
9. Create a new task thread.

The new task you created in step 9 will have ID = 1, just like the closed task does. If you click the detail button on either, you’ll see info from both on the same page, concatenated together. Not good.

This has got to be a bug, clearly the IDs should always be unique.

If you don’t stop/restart Lucee, this doesn’t happen. I suspect Lucee keeps track of the “next available ID” while it’s running, but forgets this value when it’s shutdown, and upon next start, I suspect Lucee checks all the OPEN tasks and selects the first free number, when instead it SHOULD be checking ALL tasks (both open and closed) and selecting the first free number (which, in this example, would result in a correct ID of 2).

User "cfmitrah" on dev.lucee.org verified the current version has this bug too, and asked me to open this ticket. URL over there is:

https://dev.lucee.org/t/bug-closed-task-thread-ids-reused-after-lucee-restart/8783

Thanks!