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
CBSecurity 3.9: 12 Security Middleware for ColdBox, Declared Right on the Route
Ortus Solutions today announces CBSecurity 3.9, a major step forward for securing ColdBox applications. This release adds 12 ready-made security middleware that you attach directly to routes and route groups, with no firewall rules required.
Luis Majano
Luis Majano
October
13,
2026
ACF2021 extended support ends on November 10. Is Your Application Ready?
Adobe ColdFusion 2021 reaches the end of extended support on November 10, 2026. If your application still runs on this release, the time to decide what comes next is now.
Adobe ended core support for ColdFusion 2021 on November 10, 2025. The current extended support period is best effort and does not include security patches or hotfixes. When it ends on November 10 2026, organizations will no longer have that support option from Adobe for ColdFusion 2021.
What ...
Cristobal Escobar
Cristobal Escobar
October
13,
2026
TestBox 7.2 Real Browser Testing, Smarter Reports, and Agent-Ready Results
Ortus Solutions today announces the general availability of TestBox 7.2, the biggest TestBox release in years. Built on the new bx-playwright 1.0 module, BoxLang specs can now drive a real browser, assert with web-first matchers that wait until they pass, and keep the screenshots, traces and videos of every failure. Around it, TestBox gains spec retries, a Run Failed option, a rebuilt set of HTML reporters with Ask AI on every failure, and a new Agent reporter that lets AI agents read a test run at minimal token cost.
Luis Majano
Luis Majano
October
13,
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= name=>
...
</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 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 . Glad to hear it and great job finding it!