I am so happy to announce that the last bug for BlueDragon 7 on ColdBox has been resolved. It was tricky, but it all came down to using "-" on the name of the thread being created.
If you have something like:
...
This would fail parsing in bluedragon 7 but work as normal in Adobe CF. So I had to replace and come up with better names:
...
And voila!!! It works!! So the final bug registered for ColdBox RC 2 has been resolved. Hopefully, no more bugs will creep up. If you have any, then send them in. As of now, THERE HAVE BEEN NO MORE REPORTED COLDBOX RC2 BUGS. This might cause a release soon!!
Luis
Blog
Recent Entries
Discover the tools, tricks, and techniques every modern CFML and BoxLang developer needs!
Into the Box 2026 is officially on the horizon, and it’s shaping up to be our most impactful conference yet.
Our mission this year is simple: **Make modernization approachable for everyone.** Whether you’re a seasoned ColdFusion veteran or a developer just starting your BoxLang journey, we’ve priced this event to ensure the entire community can join us in person.
Victor Campos
Victor Campos
March
05,
2026
From Lucee to Modern JVM Architectures for German Enterprises
How German companies running Lucee and CFML can evolve toward cloud-native JVM platforms
Across Germany, many enterprises rely on Lucee and CFML-based applications to run critical internal systems, customer portals, and business workflows.
Germany has one of the most active Lucee communities in Europe, supported by long-standing adoption of CFML across industries such as:
- Manufacturing
- Logistics <...
Cristobal Escobar
Cristobal Escobar
March
04,
2026
BoxLang 1.11.0 Release
We're proud to announce BoxLang 1.11.0, a highly focused performance and stability release that delivers measurable speed improvements across every BoxLang application, with zero code changes required. The team invested deeply in bytecode generation, class loading, lock management, and type casting to produce one of the most impactful runtime optimization releases to date. Alongside the performance wave, this release resolves critical concurrency bugs, hardens DateTime handling, and ships powerful new developer tooling.
Luis Majano
Luis Majano
March
04,
2026
Add Your Comment
(3)
Dec 10, 2007 10:43:21 UTC
by Vince Bonfanti
Hi Luis, We investigated this, and it's not really a bug in BD, but a difference in the way CFTHREAD works. BD creates a variable with the name of the NAME attribute, and the "-" character is not valid in a variable name (but we should give a better error message). This is similar to CFQUERY, where a variable with name specified by the NAME attribute is created. Try the following and you'll get an error on both BD and CF: <cfquery datasource="mydsn" name="myquery-#createUUID()#"> ... </cfquery> Out of curiousity, what's the purpose of giving a CFTHREAD a random name? In BD, the NAME attribute is optional, in which case BD will give the thread a system-assigned random name (I don't know if the NAME attribute is optional in CF8). In any case, we're very happy that ColdBox is running on BD 7. Cheers.
Dec 10, 2007 11:04:26 UTC
by Luis Majano
Hi Vince, Thanks for your comment. I think the tricky part of solving it, was that you could not know what the error message meant. So via "Code Smell" the name became the culprit. >Out of curiousity, what's the purpose of giving a CFTHREAD a random name? Yes, the name in CF is mandatory. So I had to create a unique name as a thread is executed by the logger or cache. >we're very happy that ColdBox is running on BD 7. So do I. The performance of ColdBox on BlueDragon is exceptional.
Dec 12, 2007 17:05:36 UTC
by Aaron Roberson
Four days later I check your blog to learn that you've discovered the solution to this "bug". Glad to hear it and great job finding it!