All work
- runAsync isn't very async compared to ACFLDEV-4398Michael Offner
- use an executorPool for runAsyncLDEV-4397
- runAsync does not capture the surrounding PageContextLDEV-3833Michael Offner
- Empty Futures via runAsync() are missing the complete() methodLDEV-2407Michael Offner
- runAsync doesn't work the same as ACF2018LDEV-2245
- Asynchronous programmingLDEV-1841Resolved issue: LDEV-1841Michael Offner
runAsync isn't very async compared to ACF
Details
Details
Assignee
Reporter
Priority
MinorLabels
New Issue warning screen
Before you create a new Issue, please post to the mailing list first https://dev.lucee.org
Once the issue has been verified, one of the Lucee team will ask you to file an issue
Activity
Pothys - MitrahSoft 21 March 2023 at 15:12
I've checked this ticket and confirmed the issue happened on the lucee latest version 5.4.0.37-SNAPSHOT.
The runAsync() didn't runs asynchronously compare to ACF-2021.
For running the 3 runAsync() operation each takes 3 seconds to complete two then executions. Lucee takes approximately 7 seconds to complete 3 runAsync(). Seems ACF takes approximately 3 seconds to complete. So ACF rans that all runAsync() in parallel. Lucee rans that all runAsync() in partially parallel.
Also ACF logs looks like, defining the new runAsync in rows, not waiting to previous one start execute.
But Lucee logs looks like, the new runAsync is defined after the previously defined one start and execute the then operation.