Issues
Remove restriction on nesting threads
Details
Assignee
UnassignedUnassignedReporter
Adam CameronAdam CameronLabels
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
Affects versions
Priority
New
Details
Details
Assignee
Reporter
Labels
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
Affects versions
Priority
Activity
David Raschper21 November 2018 at 09:13
I also tested it in 5.2.9.31, and this issue seems to be fixed.
Brett Payne-Rhodes21 November 2018 at 08:38Edited
-I can confirm that this is still an issue with Lucee 5.2.7.63
Using threads was a workaround to Lucee not having asynchronous gateways so now I'm looking for a workaround to this as well.-
My apologies... We are juggling a few configurations at the moment and I failed to check the details before I posted this comment...
What I can now confirm is that child threading is still an issue on V5.0.0.252 but appears to be fixed in V5.2.7.63 - which is great news for our async gateway workaround!
Thank you!!!
B)
See: http://blog.adamcameron.me/2015/06/cfml-i-did-not-realise-one-cannot-nest.html
Basically one cannot nest thread calls.
If there is no real reason to prohibit this and it's an artificial restriction on your part... get rid of the restriction.
I presume you were just following Adobe's lead on this one... I reckon you probably should not have.
See equivalent bug raised for ColdFusion: https://bugbase.adobe.com/index.cfm?event=bug&id=4013671
NB: probably also applies to Lucee 5, but I could not test due to LDEV-267. That issue is becoming a right pain in the arse, btw. It basically prohibits me from using Lucee 5 for 50% of my work.