Lucee 5.3.9.133 - Calling "Extension > Applications" results in timeout error

Hello,

unfortunately, after the Lucee update from version 5.3.8.206 to version 5.3.9.133, I unexpectedly encountered errors. After updating Lucee to version 5.3.9.133, I was no longer able to go to “Extension → Applications” in Server Admin. The request always ended in a timeout and a very long error message was displayed (see ZIP file). Among other things, the error message contained the following:

org.osgi.framework.BundleException The OSGi Bundle with name [lucee.image.extension] is not available in version [1.0.0.42] locally (/opt/lucee/hometix1/tomcat/lucee-server/bundles) or from the update provider (https://update.lucee.org), the following versions are available locally [1.1.0.3-SNAPSHOT, 1.0.0.38, 1.0.0.39]. /admin/ext.functions.cfm:204

This error message gave me the following idea:

  1. First I downgraded Lucee again from version 5.3.9.133 to version 5.3.8.206.
  2. Then in Lucee 5.3.8.206 I downgraded the “Image extension” from version 1.1.0.3-SNAPSHOT to version 1.0.0.42.
  3. After that I then updated Lucee from version 5.3.8.206 to version 5.3.9.133.
  4. In the server admin “Extension → Applications” could now be called without any problems.
  5. Finally, I updated the “Image extension” to version 1.2.0.0-SNAPSHOT without any problems.

Maybe this will help someone who may encounter the same problems?!

Here is the complete error message as a zipped HTML file:
server.cfm.zip (6.9 KB)

Don’t forget to tell us about your stack!

OS: Debian 9.13 - Linux
Java Version: openjdk version “11.0.14.1+1”
Tomcat Version: 9.0.62
Lucee Version: Lucee 5.3.9.133

2 Likes

@Knut Nice workaround for this.
The ticket for this issue in Jira: LDEV-3890 - Extension - Applications link in server admin times out

Until today I also thought that this was a good workaround, but… :frowning_face:

when I called “Extension > Applications” in the server admin today, the same timeout occurred again because Lucee was again looking in vain for the Image extension version 1.0.0.42

org.osgi.framework.BundleException The OSGi Bundle with name [lucee.image.extension] is not available in version [1.0.0.42] locally (/opt/lucee/hometix1/tomcat/lucee-server/bundles) or from the update provider (https://update.lucee.org), the following versions are available locally [1.1.0.3-SNAPSHOT, 1.0.0.38, 1.0.0.39]. /admin/ext.functions.cfm:204

So I had to downgrade again to Image extension version 1.0.0.42 by putting the “lucee.image.extension-1.0.0.42.lex” file in the deploy folder.

Unfortunately, I can’t currently use the image extension version 1.2.0.0-SNAPSHOT.

By the way:
If I uninstall the Image extension 1.0.0.42, I would have expected that the file “B737ABC4-D43F-4D91-8E8E973E37C40D1B-1.0.0.42.lex” would be listed under “/lucee-server/context/extensions/available”, but it is not listed. All Lex files listed in the “/lucee-server/context/extensions/available” directory are quite old and date from January and July 2021

I have this issue when upgrading 5.3.8.206 to both 5.3.9.133 or 5.3.9.141 versions. Latest error message:

Lucee [5.3.9.141] - Error (Expression)
Message request /lucee/admin/server.cfm (zip:///var/lib/tomcat9/webapps/ROOT/WEB-INF/lucee/context/lucee-admin.lar!/server.cfm) has run into a timeout (timeout: 50 seconds) and has been stopped. The thread started 90670ms ago.
Java Stacktrace
lucee.runtime.exp.RequestTimeoutException: request /lucee/admin/server.cfm (zip:///var/lib/tomcat9/webapps/ROOT/WEB-INF/lucee/context/lucee-admin.lar!/server.cfm) has run into a timeout (timeout: 50 seconds) and has been stopped. The thread started 90670ms ago.

How can help accelerate issue resolution?

Best regards,
Conrad T. Pino

@Knut @Conrad-T-Pino
Try this workaround

  1. download Image extension 1.0.0.42.lex from download page Download Lucee
  2. extract the lex file
  3. there is jar lucee.image.extension-1.0.0.42.jar placed in your_lex_file_extract_folder/jars/lucee.image.extension-1.0.0.42.jar
  4. copy and paste the jar file in your_lucee_install_folder/tomcat/lucee-server/bundles ( for commandbox looks like C:\Users\machine_name.CommandBox\server\2B06114BFFB7C32B093554189C33C457-commandbox\lucee-5.3.9.141\WEB-INF\lucee-server\bundles) directory

Now the admin Extension → Applications page open as expected without error

For production purposes 5.3.8.206 is sufficient and my preferred workaround.

AWS instances are easy enough to contribute to permanently resolving issue.

What does fix committed into release stream look like? How can I contribute?

Thank you for timely reply,
Conrad T. Pino