eXist-db does not run correctly on JDKs 12, 13, 14 and 15 #3375

dizzzz · 2020-04-18T08:26:34Z

During running unit tests, at least one test fails, only with Java13:

[WARNING] Tests run: 156, Failures: 0, Errors: 0, Skipped: 2, Time elapsed: 3.288 s - in xquery.arrays.ArrayTests
1466[WARNING] Tests run: 458, Failures: 0, Errors: 0, Skipped: 3, Time elapsed: 34.446 s - in xquery.xquery3.XQuery3Tests
1467[INFO] Tests run: 58, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 33.929 s - in xquery.optimizer.OptimizerTests
1468[INFO] 
1469[INFO] Results:
1470[INFO] 
1471[ERROR] Errors: 
1472[ERROR]   VariableByteStreamTest.copyTo:82 » ArrayIndexOutOfBounds Index 3106157 out of ...
1473[INFO] 
1474[ERROR] Tests run: 4673, Failures: 0, Errors: 1, Skipped: 102
1475[INFO]

The text was updated successfully, but these errors were encountered:

adamretter · 2020-04-20T17:42:30Z

Just to let you know @dizzzz I am digging into this. It's a tricksy one...

dizzzz · 2020-04-21T09:40:33Z

@adamretter the issue is not visible in all PRs....

adamretter · 2020-04-21T09:44:39Z

@dizzzz Indeed. The issue I am tracing appears to be non-deterministic on JDK 13 :-/ I am still not sure I believe it!

reinhapa · 2020-07-06T14:25:57Z

@adamretter do we have something like code coverage in the build? We got something similar in our build when using jacoco...

adamretter · 2020-07-06T16:59:41Z

@reinhapa No, there is no code coverage in that build or any other form of bytecode instrumentation that I am aware of.

I do have a branch where I introduce JaCoCo, but that is separate... and that has other problems... #3341

adamretter · 2020-09-14T22:13:04Z

I finally managed to isolate the issue to an independent stripped down test case - https://github.com/adamretter/vbe-test

Still it's a mystery right now that I trying to understand, but much less code to look through now at least.

reinhapa · 2020-09-15T05:01:15Z

@adamretter I wil try to take a look into this

adamretter · 2020-09-15T13:45:11Z

Looks like a JIT issue with HotSpot JDKs. Versions 12, 13, 14, and 15 are affected - https://github.com/adamretter/vbe-test#testing-results

eXist-db's Variable Byte Encoding implementation would need to be replaced to fix this at the eXist-db end.

adamretter · 2020-09-15T18:25:15Z

Thanks to @reinhapa for helping us report the JDK issue - https://bugs.openjdk.java.net/browse/JDK-8253191

dizzzz · 2020-10-19T17:54:57Z

see #3545

…ob to fail. See eXist-db#3375

joewiz · 2020-11-23T18:34:34Z

During the community call @wolfgangmm said he wanted to have a look at this

joewiz · 2021-01-04T19:16:41Z

During today's Community Call @wolfgangmm said he is looking at this

dizzzz · 2021-04-08T19:41:10Z

I'd vote to update the PR to ignore java 12-13-14-15 and pull this in as-is.

StephanMa · 2021-06-28T10:52:51Z

Dear Team,

it seems that this issue was recently fixed (2020) for Java 15.0.2.
Unfortunately eXist is not able to run with Java15 because of "Error Code: 13".
Is this still intended?

adamretter · 2021-06-28T11:04:17Z

@StephanMa Can you tell us which platform, which JDK, and what you are running to get Error Code: 13 please?

StephanMa · 2021-06-28T11:23:43Z

Mac M1
macOS Big Sur 11.4
JDK 15.0.2
trying to start eXist via ./startup.sh

Building via maven works fine... but I cannot run it due error 13

joewiz · 2021-06-28T16:19:25Z

@StephanMa Which JDK distribution?

adamretter · 2021-06-28T18:45:05Z

@StephanMa Any chance of a screenshot showing the error 13?

StephanMa · 2021-06-29T04:55:10Z

Will attach all the needed infos today

StephanMa · 2021-06-29T08:22:35Z

@adamretter Please see attached file

adamretter · 2021-06-29T09:32:52Z

@StephanMa Ah ha! Thanks that explains it.

So eXist-db only checks the major Java version, see https://github.com/eXist-db/exist/pull/3545/files#diff-7c6977667d2de8c09c5d46280134525d516cff8a0a43552b042cea303dfe8819R30

If this is fixed in Java 15.0.2, then we should update the check to permit that version.

In the mean time, your options are JDK 8 - 11.

…r example. JDK 15.0.2 should be ok now See eXist-db#3375

adamretter · 2021-06-29T15:27:54Z

@StephanMa I have a fix for you here - #3960

…r example. JDK 15.0.2 should be ok now See eXist-db#3375

StephanMa · 2021-06-29T16:18:21Z

Thank you… will give it a try

dizzzz · 2021-06-29T19:19:51Z

I am sure we actually implemented this way on purpose; for most end-users the 3rd digit it just to complex to understand; it is much more clear just to block java 12,13,14 and 15 ; from a communication perspective imo this is better. Java15 is EOL and should not be used anyway.

line-o · 2021-06-29T22:18:03Z

I agree with @dizzzz the communications overhead we might get with this change does not justify the gain to support a patch of a Java version that is no longer supported anyway.
@StephanMa do you really need this?

…r example. JDK 15.0.2 should be ok now See eXist-db#3375

* 'develop' of github.com:eXist-db/exist: Bump caffeine from 2.9.1 to 2.9.2 [bugfix] Make the Compatible Java Version Check more fine-grained. For example. JDK 15.0.2 should be ok now See eXist-db#3375 Update IntelliJ run configurations for 5.4.0-SNAPSHOT [maven-release-plugin] prepare for next development iteration [maven-release-plugin] prepare release eXist-5.3.0 Only run the github-release-plugin when mvn release:perform is performed Bump github-release-plugin from 1.1.1 to 1.4.0 [fix] docker ci add license check hotfix(docker): add license header to xml fixtures # Conflicts: # exist-ant/pom.xml # exist-core/pom.xml # exist-distribution/pom.xml # exist-docker/pom.xml # exist-jetty-config/pom.xml # exist-parent/pom.xml # exist-samples/pom.xml # exist-service/pom.xml # exist-start/pom.xml # extensions/contentextraction/pom.xml # extensions/exiftool/pom.xml # extensions/expath/pom.xml # extensions/exquery/modules/pom.xml # extensions/exquery/modules/request/pom.xml # extensions/exquery/pom.xml # extensions/exquery/restxq/pom.xml # extensions/indexes/lucene/pom.xml # extensions/indexes/ngram/pom.xml # extensions/indexes/pom.xml # extensions/indexes/range/pom.xml # extensions/indexes/sort/pom.xml # extensions/indexes/spatial/pom.xml # extensions/modules/cache/pom.xml # extensions/modules/compression/pom.xml # extensions/modules/counter/pom.xml # extensions/modules/cqlparser/pom.xml # extensions/modules/example/pom.xml # extensions/modules/exi/pom.xml # extensions/modules/expathrepo/pom.xml # extensions/modules/file/pom.xml # extensions/modules/image/pom.xml # extensions/modules/jndi/pom.xml # extensions/modules/mail/pom.xml # extensions/modules/persistentlogin/pom.xml # extensions/modules/pom.xml # extensions/modules/process/pom.xml # extensions/modules/scheduler/pom.xml # extensions/modules/simpleql/pom.xml # extensions/modules/sql/pom.xml # extensions/modules/xmldiff/pom.xml # extensions/modules/xslfo/pom.xml # extensions/pom.xml # extensions/security/activedirectory/pom.xml # extensions/security/iprange/pom.xml # extensions/security/ldap/pom.xml # extensions/security/pom.xml # extensions/webdav/pom.xml # extensions/xqdoc/pom.xml # pom.xml

…r example. JDK 15.0.2 should be ok now See #3375

duncdrum · 2022-01-31T15:21:12Z

@adamretter @dizzzz i think this one can be closed

adamretter · 2022-01-31T15:28:48Z

@duncdrum But the issue is not fixed!

dizzzz added bug issue confirmed as bug enhancement new features, suggestions, etc. labels Apr 18, 2020

adamretter added this to the eXist-5.2.1 milestone Apr 20, 2020

line-o added the high prio label Jul 13, 2020

adamretter changed the title ~~[feature] Make eXist-db Java13 compliant~~ [feature] Make eXist-db run on JDKs 12, 13 and 14 Sep 15, 2020

adamretter changed the title ~~[feature] Make eXist-db run on JDKs 12, 13 and 14~~ eXist-db does not run correctly on JDKs 12, 13 and 14 Sep 15, 2020

adamretter changed the title ~~eXist-db does not run correctly on JDKs 12, 13 and 14~~ eXist-db does not run correctly on JDKs 12, 13, 14 and 15 Sep 15, 2020

joewiz mentioned this issue Sep 29, 2020

Block startup for Java 12-15 to protect from data corruption #3545

Merged

adamretter added a commit to adamretter/exist that referenced this issue Oct 19, 2020

[bugfix] eXist-db is not compatible with JDK 14, so allow Travis CI j…

d790e4a

…ob to fail. See eXist-db#3375

adamretter mentioned this issue Oct 19, 2020

Allow Travis CI JDK14 job to fail #3572

Merged

line-o modified the milestones: eXist-5.2.1, eXist-6.0.0 Jun 28, 2021

adamretter added a commit to adamretter/exist that referenced this issue Jun 29, 2021

[bugfix] Make the Compatible Java Version Check more fine-grained. Fo…

430ba5e

…r example. JDK 15.0.2 should be ok now See eXist-db#3375

adamretter mentioned this issue Jun 29, 2021

Make the Compatible Java Version Check more fine-grained #3960

Merged

adamretter added a commit to adamretter/exist that referenced this issue Jun 29, 2021

[bugfix] Make the Compatible Java Version Check more fine-grained. Fo…

ad705f4

…r example. JDK 15.0.2 should be ok now See eXist-db#3375

adamretter added a commit to adamretter/exist that referenced this issue Jul 30, 2021

[bugfix] Make the Compatible Java Version Check more fine-grained. Fo…

1978205

…r example. JDK 15.0.2 should be ok now See eXist-db#3375

adamretter added a commit that referenced this issue Dec 13, 2021

[bugfix] Make the Compatible Java Version Check more fine-grained. Fo…

51681a6

…r example. JDK 15.0.2 should be ok now See #3375

adamretter modified the milestones: eXist-6.0.0, eXist-7.0.0 Feb 14, 2022

joewiz mentioned this issue Mar 31, 2022

[Troubleshooting]: vanilla homebrew installation with opnJDK 18 fails to start #4297

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

eXist-db does not run correctly on JDKs 12, 13, 14 and 15 #3375

eXist-db does not run correctly on JDKs 12, 13, 14 and 15 #3375

dizzzz commented Apr 18, 2020

adamretter commented Apr 20, 2020

dizzzz commented Apr 21, 2020

adamretter commented Apr 21, 2020

reinhapa commented Jul 6, 2020

adamretter commented Jul 6, 2020 •

edited

adamretter commented Sep 14, 2020

reinhapa commented Sep 15, 2020

adamretter commented Sep 15, 2020 •

edited

adamretter commented Sep 15, 2020

dizzzz commented Oct 19, 2020

joewiz commented Nov 23, 2020

joewiz commented Jan 4, 2021

dizzzz commented Apr 8, 2021

StephanMa commented Jun 28, 2021

adamretter commented Jun 28, 2021

StephanMa commented Jun 28, 2021

joewiz commented Jun 28, 2021

adamretter commented Jun 28, 2021

StephanMa commented Jun 29, 2021

StephanMa commented Jun 29, 2021

adamretter commented Jun 29, 2021

adamretter commented Jun 29, 2021

StephanMa commented Jun 29, 2021

dizzzz commented Jun 29, 2021

line-o commented Jun 29, 2021

duncdrum commented Jan 31, 2022

adamretter commented Jan 31, 2022

eXist-db does not run correctly on JDKs 12, 13, 14 and 15 #3375

eXist-db does not run correctly on JDKs 12, 13, 14 and 15 #3375

Comments

dizzzz commented Apr 18, 2020

adamretter commented Apr 20, 2020

dizzzz commented Apr 21, 2020

adamretter commented Apr 21, 2020

reinhapa commented Jul 6, 2020

adamretter commented Jul 6, 2020 • edited

adamretter commented Sep 14, 2020

reinhapa commented Sep 15, 2020

adamretter commented Sep 15, 2020 • edited

adamretter commented Sep 15, 2020

dizzzz commented Oct 19, 2020

joewiz commented Nov 23, 2020

joewiz commented Jan 4, 2021

dizzzz commented Apr 8, 2021

StephanMa commented Jun 28, 2021

adamretter commented Jun 28, 2021

StephanMa commented Jun 28, 2021

joewiz commented Jun 28, 2021

adamretter commented Jun 28, 2021

StephanMa commented Jun 29, 2021

StephanMa commented Jun 29, 2021

adamretter commented Jun 29, 2021

adamretter commented Jun 29, 2021

StephanMa commented Jun 29, 2021

dizzzz commented Jun 29, 2021

line-o commented Jun 29, 2021

duncdrum commented Jan 31, 2022

adamretter commented Jan 31, 2022

adamretter commented Jul 6, 2020 •

edited

adamretter commented Sep 15, 2020 •

edited