JavaLoader throws exception loading Apache Tika library

Description

(NB: The Affected version is 5.3.5.26-SNAPSHOT and later. This is not listed in the "Affects version" field so I chose the earliest affected version available.)

Starting with 5.3.5.26-SNAPSHOT (and including the latest 5.3.6.13-SNAPSHOT), attempting to load the current Apache Tika library using JavaLoader(1.2), results in lucee.runtime.exp.NativeException: Provider for class javax.xml.parsers.SAXParserFactory cannot be created.

Rolling back to 5.3.5.25-SNAPSHOT fixes the issue.

Steps to Reproduce

Place JavaLoader and the tika app jar in the same folder as the following script:

On 5.3.5.25-SNAPSHOT this dumps the tika object. On 5.3.5.26-SNAPSHOT and above the following exception is thrown:

Environment

OpenJDK 1.8u232 Win64.

Activity

Show:
Michael Offner
July 21, 2020, 1:09 AM

Dan Lancelot
November 13, 2020, 10:31 PM

We have encountered this issue when attempting to perform pre release tests uploading and attempting to resize image files on our existing codebase (using Mura CMS) (we are currently on Lucee 5.3.2.77) running on release version of Lucee (at the time 5.3.6.61).

We are using Docker images hosted on AWS Elastic Beanstalk (ECS) for this application - and strangely we are only encountering the issue when the docker container is hosted on AWS, and not when we are running the same image locally (Docker 19.03.13 on macOS Catalina). If anyone is able to advise as to why that may be… that would be much appreciated… as we would have thought that any Java dependencies would be resolved within the Docker container, and would not be affected by the host machine OS…

 

We have confirmed that when running on the Snapshot build before this issue was introduced (5.3.5.25-SNAPSHOT) and running on the Snapshot build in which this issue was resolved (5.3.8.17-SNAPSHOT), we do not encounter this issue.

Is it possible to patch this fix in to the latest production release and create a new production release? Currently the most recent production release in which this issue is not present would appear to be 5.3.4.80 (2020-02-24), and we are keen to move to a later release which potentially resolves a number of other issues which we are currently encountering.

Zac Spitzer
November 13, 2020, 11:42 PM

5.3.8 is going to move to RC very soon, we are in the fix regression stage

Matt Levine
December 3, 2020, 6:46 AM

Any new on when a release candidate with this fix will be released?

Zac Spitzer
December 3, 2020, 7:01 AM

I don’t know the schedule

But at this stage of the cycle, you might as well consider the latest SNAPSHOT a release candidate

the only known regressions are minor

https://luceeserver.atlassian.net/issues/?jql=labels %3D reg538 ORDER BY status DESC

Fixed

Assignee

Michael Offner

Reporter

Julian Halliwell

Priority

New

Labels

Fix versions

Sprint

5.3.8 Sprint 3

Affects versions