Extensions with OSGi wiring issues cannot be updated without manually purging installed files
Description
Environment
Attachments
- 09 Nov 2021, 08:35 pm
- 09 Nov 2021, 08:35 pm
relates to
Activity
Pothys - MitrahSoft 11 November 2021 at 07:14
I have checked this ticket and confirmed the issue happened on the lucee latest version 5.3.9.14-SNAPSHOT too. While uploading the MSSQL 9.5.0 extension file with OSGI error, throws the above-mentioned error and removed the extension from installed extensions. But it leaves the org.lucee.mssql-9.5.0.preview_jre11.jar file in the lucee-server/bundles folder. After that uploading, the valid 9.5.0 extension file throws the same error.
After deleting the mssql-9.5.0.jar file from the bundles folder and restarting the lucee now uploading valid 9.5.0 extension file was installed successfully.
lucee.runtime.exp.NativeException: Unable to resolve org.lucee.mssql [96](R 96.0): missing requirement [org.lucee.mssql [96](R 96.0)] osgi.wiring.package; (osgi.wiring.package=com.azure.core.credential) Unresolved requirements: [[org.lucee.mssql [96](R 96.0)] osgi.wiring.package; (osgi.wiring.package=com.azure.core.credential)]
at org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:4368)
at org.apache.felix.framework.Felix.startBundle(Felix.java:2281)
at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:998)
at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:984)
at lucee.loader.osgi.BundleUtil.start(BundleUtil.java:112)
at lucee.loader.osgi.BundleUtil.start(BundleUtil.java:108)
at lucee.runtime.osgi.OSGiUtil._start(OSGiUtil.java:1214)
at lucee.runtime.osgi.OSGiUtil._startIfNecessary(OSGiUtil.java:1167)
at lucee.runtime.osgi.OSGiUtil.startIfNecessary(OSGiUtil.java:1162)
at lucee.runtime.osgi.OSGiUtil._loadBundle(OSGiUtil.java:540)
at lucee.runtime.osgi.OSGiUtil.loadBundle(OSGiUtil.java:492)
at lucee.commons.lang.ClassUtil.loadClassByBundle(ClassUtil.java:155)
at lucee.transformer.library.ClassDefinitionImpl.getClazz(ClassDefinitionImpl.java:110)
at lucee.runtime.config.XMLConfigAdmin.setClass(XMLConfigAdmin.java:6609)
at lucee.runtime.config.XMLConfigAdmin._updateJDBCDriver(XMLConfigAdmin.java:1799)
at lucee.runtime.config.XMLConfigAdmin.updateRHExtension(XMLConfigAdmin.java:5001)
at lucee.runtime.config.XMLConfigAdmin.updateRHExtension(XMLConfigAdmin.java:4690)
at lucee.runtime.config.XMLConfigAdmin._updateRHExtension(XMLConfigAdmin.java:4672)
at lucee.runtime.tag.Admin.doUpdateRHExtension(Admin.java:4312)
at lucee.runtime.tag.Admin._doStartTag(Admin.java:763)
at lucee.runtime.tag.Admin.doStartTag(Admin.java:352)
at ext_applications_upload_cfm966$cf.call(/admin/ext.applications.upload.cfm:53)
at lucee.runtime.PageContextImpl._doInclude(PageContextImpl.java:1034)
at lucee.runtime.PageContextImpl._doInclude(PageContextImpl.java:926) Details
Assignee
Michael OffnerMichael OffnerReporter
dan.switzer@givainc.comdan.switzer@givainc.comPriority
NewNew Issue warning screen
Before you create a new Issue, please post to the mailing list first https://dev.lucee.org
Once the issue has been verified, one of the Lucee team will ask you to file an issue
Affects versions
Details
Details
Assignee
Reporter
Priority
NewNew Issue warning screen
Before you create a new Issue, please post to the mailing list first https://dev.lucee.org
Once the issue has been verified, one of the Lucee team will ask you to file an issue
I've been working on getting the MSSQL 9 drivers working in Lucee and ran into a bug with Lucee that caused me to waste several days trying to track down what I thought was a weird OSGi issue, which ended up being due to the fact that Lucee was not updated the bad extension (LEX file) with the fixed extension.
When you deploy a Lucee extension (either by copying into the
/deployfolder or using the extension upload in the Admin) that has a JAR file that has OSGi issues, Lucee leaves the installed files left in the file system. If you then try to update the extension, the previously installed files are not replaced, which leads to no updates happening.Because I'm new to using OSGi, I spent way too much time troubleshooting issues with my package that didn't actually exist, but were caused because Lucee was not actually updating the extension like I thought it was.
To see this behavior in action, I've uploaded two files:
— This is an extension with OSGi errors in the JAR.
— This is an extension with a properly configured OSGi JAR.
In a new Lucee install (or one where this extension has not been installed), unzip the
file and then go to the Lucee Admin and upload the
org.lucee.mssql-9.5.0.preview_jre11.lexextension. When you upload the file, you should see an error like the following:Now, try unzipping the
and uploading the good org.lucee.mssql-9.5.0.preview_jre11.lex extension. You should see the same error. This is because the extension's JAR file is still deployed and so when you try to upload the fixed extension, the JAR is not replaced resulting in getting the same deployment errors.
To resolve the issue, you must locate the installed files, stop Lucee, remove the files, then restart Lucee. For example, the following illustrates the steps required assuming a Linux OS and that Lucee is installed in the
/optfolder and running Lucee under Tomcat:Stop Lucee:
service tomcat.service stopFind the installed file, with something like:
find /opt -name *mssql*Find the path to the JAR file, and delete it:
rm -f /opt/lucee/config/server/lucee-server/bundles/org.lucee.mssql*.jarFind the path to the
cfclassescache folders and remove them, for example:rm -fr /opt/lucee/config/web/d2d154bed8cf37f7d84aac7b28f70446/cfclasses/Start Lucee:
service tomcat.service startAfter you have cleaned up the extension, try installing the good org.lucee.mssql-9.5.0.preview_jre11.lex and this time it will install.
While this is only going to affect people developing Extensions, it was a real pain. Not having a lot of experience with OSGi, I really assumed the problem was with attempt to re-bundle the JAR as OSGi and not a caching issue with a previously deployed extension.