Amazon S3 Extension Not Installed, but s3:// Paths Still Work in Lucee

dev support
1

In the Lucee Admin, it shows that the Amazon S3 extension is not installed.
However, I am still able to use s3:// paths in my CFML code (for example with <cffile>), and everything is working without errors.

Is this expected behavior?

  • Does the Amazon S3 extension actually need to be installed to use s3:// paths in Lucee?
  • Or could this be a bug in the Lucee Admin where the extension is installed but not being recognized or displayed correctly?

Any clarification would be appreciated.

Don’t forget to tell us about your stack!

OS: Windows Server 2019 (10.0) 64bit
Java Version: 21.0.7 (Eclipse Adoptium) 64bit
Tomcat Version: Apache Tomcat/11.0.6
Lucee Version: 6.2.4.24

2

Did you have it previously installed?

Do you have this in your .CFConfig.json ?

  "resourceProviders": [
    {
      "bundleName": "org.lucee.s3.extension",
      "arguments": {
        "lock-timeout": "10000"
      },
      "bundleVersion": "2.0.3.0",
      "scheme": "s3",
      "class": "org.lucee.extension.resource.s3.S3ResourceProvider"
    }
  ],
3

I did had it installed, I found it odd that it was missing from the admin page. Yes it is in the config file. It’s using version 0.9.4.156.

Can I upgrade/install this extension through the Lucee Admin without issue or should I do this a different way since it’s set in the config file and obviously already installed?

Also could that S3 extension version be throwing this warning:

[WARN] HttpMethodReleaseInputStream - Attempting to release HttpMethod in finalize() as its response data stream has gone out of scope. This attempt will not always succeed and cannot be relied upon! Please ensure response data streams are always fully consumed or closed to avoid HTTP connection starvation.
[WARN] HttpMethodReleaseInputStream - Successfully released HttpMethod in finalize(). You were lucky this time… Please ensure response data streams are always fully consumed or closed.

4

wow, truly ancient from Nov 2022! latest is 2.0.3.0

https://download.lucee.org/#17AB52DE-B300-A94B-E058BD978511E39E

this is a older install which has been upgraded yeah, or you copied config across?

I’d suggest doing a clean install, then diff the new CFConfig.json with your old one and only copy across the config you want, don’t copy the old extensions, I think that’s how you ended up with this mess

5

6 posts were split to a new topic: Resource leaks with s3 and cfimage