I'm using the default Lucee docker image (`lucee/l...
# lucee
a
I'm using the default Lucee docker image (
lucee/lucee:5.3.9.166-nginx
). Requests are timing out @ 50sec, which is the default in server admin. But... we're setting
setting requesttimeout=300
at the beginning of the script in question. Same code using a
ortussolutions/commandbox
container and getting it to strum-up a Lucee 5.3.9.166 instance respects the
300
timeout as one would expect. I've not dug into this much yet, but is that setting off any recollection with anyone?
Also relevant: if I change the timeout in Lucee admin to say 59, then the req times out in 59sec, so that's def the value it's using.
a
It's not coming from Nginx, it's coming from Lucee. It's literally Lucee's request timeout, as controlled by the timeout setting in Admin. But good suggestion. I also needed to tweak that for another situation 😉 TIL: more than I wanted to about Nginx (the amount I wanted to learn about it being zero, that said)
d
@Adam Cameron Does adding a semi-colon to the line change anything? I know there are some corner cases where semi-colons are required (but can't remember them because I always use semi-colons to end an instruction).
⭐ 1
a
ah there is one in the actual code.
note: this all works 100% fine & as expected when using the Ortus image
I've been working on this container build all afternoon, and it appears to have been a transient one. I cannot reproduce it any more. So whilst it's "interesting" maybe, there's better things to concern ourselves with, I reckon. Cheers for the input from @zackster and @dswitzer: I appreciate it.