Upgrade from 4.5 to 5 via JAR replace has multiple issues

Description

Upgrading from Lucee 4.5 to 5 via the JAR replacement method creates multiple issues:

Issue 1

Any S3 mapping or attempt to use and S3 resource generates the following error:

06-Feb-2016 15:56:27.328 SEVERE [http-nio-8888-exec-2] org.apache.catalina.core.StandardWrapperValve.invoke Allocate exception for servlet CFMLServlet javax.servlet.ServletException: No S3 Resource installed! at lucee.commons.io.res.type.s3.S3ResourceProvider.notInstalled(S3ResourceProvider.java:108) at lucee.commons.io.res.type.s3.S3ResourceProvider.notInstalledEL(S3ResourceProvider.java:112) at lucee.commons.io.res.type.s3.S3ResourceProvider.getResource(S3ResourceProvider.java:46) at lucee.commons.io.res.ResourcesImpl.getResource(ResourcesImpl.java:81) at lucee.runtime.config.ConfigImpl.getResource(ConfigImpl.java:2202) at lucee.runtime.config.ConfigWebUtil.getExistingResource(ConfigWebUtil.java:350) at lucee.runtime.MappingImpl.<init>(MappingImpl.java:137) at lucee.runtime.config.XMLConfigWebFactory.loadMappings(XMLConfigWebFactory.java:1530) at lucee.runtime.config.XMLConfigWebFactory.load(XMLConfigWebFactory.java:387) at lucee.runtime.config.XMLConfigWebFactory.newInstance(XMLConfigWebFactory.java:262) at lucee.runtime.engine.CFMLEngineImpl.loadJSPFactory(CFMLEngineImpl.java:439) at lucee.runtime.engine.CFMLEngineImpl.addServletConfig(CFMLEngineImpl.java:389) at lucee.loader.engine.CFMLEngineWrapper.addServletConfig(CFMLEngineWrapper.java:88) at lucee.loader.engine.CFMLEngineFactory.getInstance(CFMLEngineFactory.java:205) at lucee.loader.servlet.CFMLServlet.init(CFMLServlet.java:44) at org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1231) at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1144) at org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:817) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:135) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:106) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:502) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:142) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:79) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:88) at com.seefusion.SeeFusionValve.invoke(SeeFusionValve.java:49) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:518) at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1091) at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:673) at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1500) at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1456) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) at java.lang.Thread.run(Thread.java:745)

Even though the S3 extension is reported as installed in the admin.

If a mapping is used on a site then it reports the above message for every single request to that site.

Various attempts to uninstall and reinstall the S3 extension, in various ways, did not resolve this issue.

Issue 2

All MySQL datasource (maybe others as well) are reported as "Other - JDBC Driver (deprecated)” and when you attempt to edit them you get a Lucee error message stating key [MySQL] doesn't exist with the following stacktrace:

Stacktrace The Error Occurred in /home/travis/build/lucee/Lucee/core/src/main/cfml/context/admin/services.datasource.create.cfm: line 129 called from /home/travis/build/lucee/Lucee/core/src/main/cfml/context/admin/services.datasource.cfm: line 83 called from /home/travis/build/lucee/Lucee/core/src/main/cfml/context/admin/web.cfm: line 389

The path reported in this stacktrace is not related to the system on which it is running for some reason.

Looking at the "bundles" in the admin shows that both the MySQL driver JAR 5.1.20 and 5.1.38 are both present and the extension reports in the admin as requiring an "update". Attempting to update the extension results in an error message similar to:

`/opt/lucee/tomcat/lucee-server/context/extensions/installed/siajegyhw5jp.lex (No such file or directory)

To resolve this I did the following steps:

1) Stop Lucee / Tomcat
2) Deleting everything in the felix-cache directory
3) Deleting the com.mysql.jdbc-5-1-20.jar file from the bundles directory
4) Deleting the mysql-5.1.20.lex file from the extensions/available directory
5) Start Lucee / Tomcat

Environment

None

Activity

Show:
Fixed

Details

Assignee

Reporter

Priority

Labels

New 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

Created 7 February 2016 at 21:26
Updated 19 September 2016 at 15:41
Resolved 19 September 2016 at 15:41

Flag notifications