and yes there are plans afoot to remove it from being a single point of failure

we are back in business

I can confirm that commandbox-lex works again as well using the API @alexpixl8, ta

thx guys, we then try a redeploy

Anyone using ngrok for exposing local hosts in combination with a urlrewrite.xml? In my case all static files are served through ngrok, but everything running through the urlrewrite.xml returns a 404. Happening with PresideCMS as application.

Is there a way to deploy lex files as part of a war file?

If I'm using the lucee.war (which has all the "primary" extensions included). For what reason is lucee connecting to lucee.org domains? I'm trying to remove any reliance on this connection to avoid a repeat of yesterday's (and April's) lucee extension server failure.

To check for updates

say I ask my database to kill all its open connections, can I inform lucee about this and ask lucee to reopen a connection for some datasource?

Does anyone still use Gmail as a mail server to send emails from Lucee apps? Now that they disabled the ability to use "less secure apps in the Admin console" it seems one cannot simply setup Gmail to use as an SMTP server any longer? O365 doing the same in October.

What might cause the dump of the same Java object on one Lucee 5.3.9.133 instance to include a section

bundle-info

at the bottom, and a dump of the same object on a different Lucee 5.3.9.133 instance to not include that section? Both built from the same

lucee/lucee:5.3.9.133-nginx

Docker image. The Docker config for each is superficially different, but not in any way that ought to impact this. IE: one dump ends with: The other ends with:

What behaviour in Lucee which is too "clever" would you like to see gone in 6.0?

Bit stumped on what could be going on with a Lucee upgrade from 5.3.8.206 to 5.3.9.141. I upgraded one Linux server, and everything worked fine, so I upgraded a second one and this broke any query to MySQL. I looked in the exception log to determine this as my custom error page just blows up and displays:

Lucee [5.3.9.141] - Error (Expression) Message variable [ERROR] doesn't exist.

I've rolled back to 8.206 and everything works fine again. I'd pass this off as something I need to update if it was just my queries to MySQL, but it seems really odd that the custom error handler no longer works correctly either. I notice that the JDK on the 2nd server is older than the first, 1.8.0_202 (AdoptOpenJdk) 64bit versus 1.8.0_292 (AdoptOpenJDK) 64bit. I'll try to get this updated this evening but wondering if anyone else has run into this and if they have any ideas for other things to check other than updating the JDK. Both servers are running the same MYSQL driver, 8.0.24. I tried version 5.3.9.133 also and same issue so I looked through the change log for 9.133 and nothing is jumping out at me as to what is causing the error handler to fail.

@zackster What I would like to see is the language advance to be more IDE friendly, easier to lint. Oh, and easier to build a debugger for VSCode and beyond.

Does anyone have a good workflow for testing new Lucee builds? @bdw429s sent me something a while ago that worked well with CommandBox, but I've somehow misplaced those instructions. I'm really wanting to fire up the testbox tests to run a specific test suite, preferably in the browser so I can do some tracking.

I'd like to add ftp and sftp, even ftps to the lucee CI process, @dswitzer suggested greenmail which was great for smtp, pop, imap etc https://luceeserver.atlassian.net/browse/LDEV-4028 googling this is a nightmare, anyone got any tips? i.e I'm after a docker image which provides these services

Is there a way in lucee to tell how many emails are in the spool? Like in acf I can just count the files in the spool folder.

@zackster Why are some of the unit tests in the Lucee code base being excluded from running, like

_Mail.cfc?

? Any test starting with an underscore doesn't run, but I'm not sure why they would be getting excluded.

I'm curious if my sentiments on this ticket are shared by anyone else? https://luceeserver.atlassian.net/browse/LDEV-4074 Is a cftimeout tag useful or just unnecessary? I do like the

onTimeout

convention, but I'd just as soon see that sort of thing added to cfthread directly. Precedent in the language however would make me want the timeout to raise an exception to match tags like cflock'd default behavior.

Churned thru some of the pending patches for 6.0 this weekend https://github.com/lucee/Lucee/compare/6.0.0.192...6.0.0.201 getting there!

I just submitted pull requests for the 5.3 and 6.0 branches to so that CFMAIL uses

quoted-printable

encoding for all HTML parts. This resolves https://luceeserver.atlassian.net/browse/LDEV-4039.

Has anyone seen an issue with recent versions of Lucee 5.3 where joining all threads created still has some threads in a running state and the timeout has not be hit? We recently migrate our application from ACF to Lucee and in one of our background jobs, we spawn a bunch of threads to check some email mailboxes. What I'm seeing is that occassionally some of the threads are still in a "RUNNING" state after the join, even though the join is well short of the timeout. The join should be only timing out after about 15 minutes, but in these cases the join happens after about 30-60 seconds and some threads are still running. Someone else posted a message in the forums asking about join/running states just a few days ago: https://dev.lucee.org/t/threads-still-in-running-status-after-join/10644/3 Maybe the issue is within Java. I'm not seeing anything in the Lucee source code that would look like an obvious issue.

<CFIMPORT prefix="ld" taglib="/#myMapping#/widgets"> Is there any way possible to make cfimport work with a variable like this? I try but it fails.

Is cfdump debug logging not working anymore for anyone else?

Quick Q that I will ask and then go off and try to answer, but in case anyone knows off the top of their head.

<cfsetting requesttimeout="0">

for CF this is actively documented as meaning "If you specify 0 as the value, timeout is disabled for the request." (ref: https://helpx.adobe.com/coldfusion/cfml-reference/coldfusion-tags/tags-r-s/cfsetting.html). Lucee's docs (https://docs.lucee.org/reference/tags/setting.html) do not mention this special meaning at all. Can anyone confirm that the behaviour exists, and it's a documentation oversight, or if it's a difference in behaviour between CF and Lucee. Please do not waste your time investigating this... I can do that and I don't want ppl doing my work for me. Just wondering if anyone already knows. Cheers. I will report back with my findings shortly anyhow. Cheers.

Hi, I am sure I have had this issue before but cannot seem to figure it out. New AWS EC2 instance running Ubuntu 18.04. Installed Apache 2.4. Installed Lucee (latest) using the standard install with mod connector options. Try to load a site and I get 503 - “The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.” I may have missed a step but surely I should be able to access the lucee admin on the default site?