also, anyone else running lucee on https://adoptium.net/ at the moment ?

Installer ships with adoption! Java 17 still TODO

anyone encountered this? https://stackoverflow.com/questions/37416243/mock-email-using-green-mail-error-couldnt-connect-to-host-port-localhost-3 trying to get greenmail up for lucee 6 and ci with github actions https://github.com/lucee/Lucee/blob/6.0/.github/workflows/main.yml#L46 https://github.com/lucee/Lucee/runs/7092534619?check_suite_focus=true#step:17:1394

Looking to spin up a small in functionality app in AWS with • Lucee • PostgreSQL • Redis • S3 • SES • SQS • Cognito • API Gateway • Couple of EC2 instances Does anyone see any problems doing this? Anything to watch out for? This has the potential for scaling quickly, so it'll need a load balancer and multiple instances. Any tips would be appreciated. Lucee would need to handle some of the data I/O and we can build Lambdas for a lot of the rest.

I've run ACF in prod with 50-ish servers x 8 instances each behind F5. Never done this kind of thing with Lucee before.

Please use a thread

Googled this a bit but didn't find anything. One can set the initial Lucee admin password via

lucee-server/context/password.txt

. We're currently using a plain-text value here, which is a bit of a security shortcoming, and was wondering if one can provide the hash of the pwd instead of the clear-text one somehow? Tangentially related, it's not uncommon for Docker images to support environment variables for this sort of thing (eg https://hub.docker.com/_/mysql, and scroll down to "Environment Variables"). The Lucee image page on Dockerhub doesn't mention anything like this, but wondering if there's anything that's just not documented..? (NB: this is specifically a Lucee question, and nowt to do with how CommandBox might do its own thing even betterer)

big shout out to @Andreas for being a community support HERO! https://dev.lucee.org/t/installing-lucee-on-windows-with-xampp-apache2-without-iis-boncode-problem-with-port/10528/26

Upgraded one of our production instances to 5.3.9.141 over the weekend. We've had it in nonprod for while with no issues. The upgraded prod instance is showing very long request times, not for every request, but there seems to be a pattern when it gets hit by a lot of requests that the active requests will spike up, and profiling the requests shows something like the image below. I ramped up FusionReactors profiling settings to gather that and that seemed to make the problem much worse. CPU and heap are fine over the same period, so its not a resource issue. maxRequests is set to 200, so not hitting a limit there. The lock its waiting on 0x536669ad always seem to be the same. When I click on that, I get the last image. Any ideas how I could further troubleshoot before I take production back to 5.3.8? I have three other production servers using that and they are all still running fine and not displaying the same issue

I did a podcast interview about my role on Lucee https://teratech.com/116-lucee-6-release-features-behind-the-scenes-with-zac-spitzer/

Back to this:

this is the remote-client folder right? in

lucee-server.xml

there's

<remote-clients directory="{lucee-config}remote-client/"/>

I'm curious as to how the mail spool dir ended up with the name

remote-client

. Instead of - maybe -

mail-spool

or something a bit more on-point? However within that dir there is a subdir

open

(eg:

/usr/local/lib/serverHome/WEB-INF/lucee-web/remote-client/open

) and it seems that's the actual spool dir: I see email objects being created in there, and undelivered emails persist there until I run the task in admin. Am I reading that right? NB: that I need to ask questions like this is perhaps indicative that better dir naming might be helpful here. Contrast with CF:

cfusion/Mail/Spool

and

cfusion/Mail/Undelivr

. Easy to tell what's what there.

Does Lucee automatically perform gzip compression if the user's browser supports it or do I have to enable it somehow?

🙂, my birthday is Sunday. Will I get to try Lucee 6 beta on my birthday? 🙂

Happy birthday!

We are converting our servers from Adobe CF2018 to Lucee. I think we have run into this bug https://luceeserver.atlassian.net/browse/LDEV-1059 Is there any plan to fix this. It seems like this affects more than just functions. Any column in the query is available inside cfcs and functions called inside a query loop.

Hi, I've got strange things happening with my Lucee Docker environment: After 1 or 2 days running, Lucee forgets to execute scheduled tasks; in fact it "forgets" all of its custom configuration. If I restart my docker container all the config from the lucee-web.xml.cfm or scheduler.xml are gone (in Admin everything is empty). I found out that it thinks that the config path is /var/www/opt/lucee/web instead of /opt/lucee/web (it says so in this log file: /opt/lucee/server/lucee-server/context/logs/out.log

WEB CONTEXT (e4d04fcf8f1486030e6781b8ac00870c)

- config:/var/www/opt/lucee/web (custom setting)

- webroot:/var/www

If I do a full build (using --no-cache) it works again, but I don't know where this config path change is coming from. Any ideas? Thanks a lot! Cheers

I think you need to store the config is out of docker than make a mapping for that config. If not when you restart the docker everything is gone

One thing, if I may ask you 😉 I just started a box instance using

docker pull ortussolutions/commandbox

and

docker run -p 8080:8080 -p 8443:8443 -v "/path/to/your/app:/app" ortussolutions/commandbox

How can I now access lucee admin? Using localhost:8080/lucee/admin/web.cfm there's nothing. I think I'm still missing the entry point a bit?!? 🙈 Thanks

Just downloaded the express version of Lucee to my web server, where should I put in? Should I leave it in home/<username>/lucee/ or should i move it?

It seems like

<http://extension.lucee.org|extension.lucee.org>

is down. @zackster

@agentk we are having severe problems on our servers too since the last 1.5hr ... it doesn't load extensions probperly

Yup, if you have a process in which during deployment you’re pulling .lex files from the extension server (maybe using commandbox-lex) --- don’t deploy right now.

I have the same problem too

now when build I set the extention as ENV like this

ENV LUCEE_EXTENSIONS "66E312DD-D083-27C0-64189D16753FD6F0;name=PDF;version=1.0.0.97-RC

@agentk I think this will problem right ?

I'm on it

its coming back up server crapped out

thx @alexpixl8