http://coldfusion.com logo
Join Slack
Powered by
To check for updates
# lucee
g
To check for updates
c
Makes sense.. though if the update endpoint is non responsive.. it prevents application deployment. Do you know if it's possible to disable the update check?
z
which version of lucee?
c
Hey Zac.. 5.3.9.141 i did some digging and found https://github.com/lucee/Lucee/commit/476e0f7da746150d7fc42de3eea95c1f4ea18236#diff-c9018935d3b5f5968bb1258b7d62[…]07f7220d0cb8cc5d82dec9c6334b4R576 System.getProperty( "lucee.enable.bundle.download" ); so im trying setting LUCEE_ENABLE_BUNDLE_DOWNLOAD: false
Hmm.. didnt seem to have the desired effect, I put ONLY 5 extensions into the lucee.jar:extensions dir and after deployment, all the usual suspects are re-installed
z
that just stops the downloading of jar bundles from the update provider, it's good that's having no effect. Usually only happens when we miss a jar inside and extension or core
if you set the trace and deploy logs to info under the server admin, you should see more useful information
with 5.3.9, there are a few http calls done directlty via java, but they (finally) have 5s connection timeout, rathe than hanging
❤️ 1
c
K, I've misunderstood it's purpose then... i dont install server admin outside of dev..
z
if you want to minimise the extensions installed, start with lucee light (that's just the lucee core without any extensions)
👍 1
c
This looks promising.. what would happen if another lucee outage happened with 5.3.9.. would it be constantly be making those 5 sec requests?
z
with these 5s timeouts, if lucee can't download what it needs, it will now throw an error after 5s, instead of hanging waiting for a connection
just disable your network to test
c
Thanks for the heads up.. I'll play around with creating my own war file with lucee light..
z
I've done a lot of work on our CI build process to catch any config errors which lead to this
c
You mean leading to errors from the 5sec timeout?
z
yes and missing bundles in general
c
sweet.. It'd be great to hear your most valuable lessons learned..
z
there were for example, some cross dependencies between extensions which took a long time to eliminate. our extension CI now explicitly tests for this by using only lucee light
c
as far as I know (still getting this war file together) i really only need esapi, image, mysql, pdf s3 exensions..
As far as your ci tests, what sorts of assertions are you expecting?
z
none, coz we fixed them all!! either an osgi wiring error, missing bundle, or can't connect to update server
c
interesting.. ive just build a war using lucee light, and using the lucee-image-extension.. but seeing Lucee 5.3.9.141 Error (template) Message undefined tag [cfimage] is there an extension for tag based images code?
z
nup, all image functions are in the image extension
c
hmm.. i must have stuffed something..
z
did you bump the deploy log level to info like i suggested?
c
well short answer.. no, longer answer, I don't have admin enabled outside of development env
I'll try to enable admin in our staging env tomorrow.. its 10pm here and I'm done with whack-a-mole
Thanks for your suggestions Zac... much appreciated!
👍 1
So I got my war file deploying with no CI failures.. it seems I needed to copy the lex files into 
WEB-INF/lucee-server/deploy
not 
WEB-INF/lucee-server/extensions
z
that would do it 🙂
Open in Slack
PreviousNext
Powered by