http://coldfusion.com logo
Join Slack
Powered by
I'm trying out the light lucee docker image. In on...
# lucee
j
I'm trying out the light lucee docker image. In one of my downstream image's containers, I'm getting some errors. FYI, in its Lucee admin, it shows that the S3 extension is installed. Any guesses as to what's wrong? (Lucee 5.3.10.97) https://gist.github.com/jamiejackson/b2d9d1fe68b546e7cab353a873d956cd
s
Do the versions match?
this seems to be the key line:
Copy code
"ERROR","main","05/26/2023","16:15:20","OSGi","The OSGi Bundle with name [mx4j.lite] in version [3.0.2] for [mx4j.lite:3.0.2,org.lucee.jets3t:0.9.4.0003L,s3.extension:0.9.4.114] is not available locally [ (/opt/lucee/server/lucee-server/bundles)] or from the update provider (<http://stable.lucee.org>).;org.osgi.framework.BundleException: The OSGi Bundle with name [mx4j.lite] in version [3.0.2] for [mx4j.lite:3.0.2,org.lucee.jets3t:0.9.4.0003L,s3.extension:0.9.4.114] is not available locally [ (/opt/lucee/server/lucee-server/bundles)] or from the update provider (<http://stable.l>
j
You mean the "s3.extension" version (0.9.4.114)? I'm not specifying that version so I'm not sure where it's coming from.
Fwiw, another image I've got, which uses both the S3 version I'm specifying in the gist, as well as several other extensions, doesn't have the startup problems that this image has.
s
so the only thing we know for sure is that that image wants that extension with that version and can't find it. that version of that extension is from 2017, so might be worth updating it to 0.9.4.156 or else the 2023 RC of v2
barring that, i'd look for a disconnect between downstream and the image you made
if you're 100% sure the image you have in front of you has that extension with that version, then gotta figure out why the downstream one doesn't (e.g. is it pulling in a whole different engine for some reason)
j
Well, the image throwing that error, in its admin, shows the that the version I specified is indeed installed. I don't know why Lucee would be looking for some other version, as well.
The version I specify is relatively new (if not the newest): 2.0.0.94-RC. You can see it specified here: https://gist.github.com/jamiejackson/b2d9d1fe68b546e7cab353a873d956cd#file-dockerfile-L4
s
AFAIK Lucee only calls for an extension when some code or bundle invokes it. I'm curious what mx4j.lite is
j
i think i found a remnant of an s3 reference in my lucee-web.xml.cfm template that gets placed. i'm trying without it now.
I have zero recollection of what this is/was for:
Copy code
<resources>
...
<resource-provider arguments="lock-timeout:10000;" class="lucee.commons.io.res.type.s3.S3ResourceProvider" scheme="s3"/>
</resources>
nah, didn't help.
Yeah, I don't know what's going on. It's not like I'd be invoking some explicit, old version of the s3 plugin from code. I did notice that in another downstream image, that if I installed the Hibernate extension, I also had to install the Compress extension because ORM stuff was throwing errors without it. IOW, Lucee doesn't do a great job pulling extension dependencies (at least in one instance).
So this might be some variant of that, somehow.
z
Any precompiled code? / .lar stuff
Orm and Compress are tested in isolation using light. If there's a dependancy I doubt it, unless it's older versions.
s
I'd try the same image on a hello world app and see if it still happens
j
Orm and Compress are tested in isolation using light. If there's a dependancy I doubt it, unless it's older versions.
Okay, I'll let you know if I retry the experiment to omit the compress extension.
I'd try the same image on a hello world app and see if it still happens
Yeah, I'll do that.
i think it will be tough to make a portable example of the issue, but i was able to figure out what triggers the issue (of the old version of the s3 extension and its mx4j dependency). the thread picks back up here: https://cfml.slack.com/archives/C06TA0A9W/p1687370506115319
2 Views
Open in Slack
PreviousNext
Powered by