You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2025/02/11 10:01:19 UTC
[Bug 69576] New: Tomcat doesn't start on JDK 17 due to an ExceptionInInitializerError
https://bz.apache.org/bugzilla/show_bug.cgi?id=69576
Bug ID: 69576
Summary: Tomcat doesn't start on JDK 17 due to an
ExceptionInInitializerError
Product: Tomcat 9
Version: unspecified
Hardware: PC
OS: Mac OS X 10.1
Status: NEW
Severity: normal
Priority: P2
Component: Util
Assignee: dev@tomcat.apache.org
Reporter: kevin+bugzilla@leturc.fr
Target Milestone: -----
Created attachment 39991
--> https://bz.apache.org/bugzilla/attachment.cgi?id=39991&action=edit
The full server logs during Tomcat start on JDK 17
The recent fix for CVE-2024-56337 shipped within Tomcat 9.0.99 caused error
during Tomcat start while running on JDK 17.
We also use Tomcat 9.x on JDK 11 and didn't observe the issue.
See below the exception preventing Tomcat to start:
---
2025-02-11 05:20:16 SEVERE [main]
org.apache.tomcat.util.digester.Digester.startElement Begin event threw
exception
java.lang.reflect.InvocationTargetException
at
java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native
Method)
at
java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:77)
at
java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at
java.base/java.lang.reflect.Constructor.newInstanceWithCaller(Constructor.java:500)
at
java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:481)
at
org.apache.tomcat.util.digester.ObjectCreateRule.begin(ObjectCreateRule.java:103)
at
org.apache.tomcat.util.digester.Digester.startElement(Digester.java:1278)
at
org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
at
org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanStartElementAfterName(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentScannerImpl$ContentDispatcher.scanRootElementHook(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown
Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown
Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown
Source)
at
org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
at
org.apache.tomcat.util.digester.Digester.parse(Digester.java:1559)
at
org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:623)
at
org.apache.catalina.startup.HostConfig$DeployDescriptor.run(HostConfig.java:1844)
at
java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539)
at
java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at
org.apache.tomcat.util.threads.InlineExecutorService.execute(InlineExecutorService.java:75)
at
java.base/java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:123)
at
org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java:575)
at
org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:466)
at
org.apache.catalina.startup.HostConfig.start(HostConfig.java:1584)
at
org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:312)
at
org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:109)
at
org.apache.catalina.util.LifecycleBase.setStateInternal(LifecycleBase.java:389)
at
org.apache.catalina.util.LifecycleBase.setState(LifecycleBase.java:336)
at
org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:776)
at
org.apache.catalina.core.StandardHost.startInternal(StandardHost.java:721)
at
org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:164)
at
org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1203)
at
org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1193)
at
java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at
org.apache.tomcat.util.threads.InlineExecutorService.execute(InlineExecutorService.java:75)
at
java.base/java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:145)
at
org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:749)
at
org.apache.catalina.core.StandardEngine.startInternal(StandardEngine.java:211)
at
org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:164)
at
org.apache.catalina.core.StandardService.startInternal(StandardService.java:415)
at
org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:164)
at
org.apache.catalina.core.StandardServer.startInternal(StandardServer.java:874)
at
org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:164)
at
org.apache.catalina.startup.Catalina.start(Catalina.java:739)
at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
at
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:569)
at
org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:345)
at
org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:473)
Caused by: java.lang.NoClassDefFoundError: Could not initialize class
org.apache.tomcat.util.compat.JreCompat
at
org.apache.catalina.core.StandardContext.<init>(StandardContext.java:323)
... 54 more
Caused by: java.lang.ExceptionInInitializerError: Exception
java.lang.reflect.InaccessibleObjectException: Unable to make field static
final boolean java.io.FileSystem.useCanonCaches accessible: module java.base
does not "opens java.io" to unnamed module @dcf3e99 [in thread "main"]
at
java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:354)
at
java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:297)
at
java.base/java.lang.reflect.Field.checkCanSetAccessible(Field.java:178)
at
java.base/java.lang.reflect.Field.setAccessible(Field.java:172)
at
org.apache.tomcat.util.compat.JreCompat.<clinit>(JreCompat.java:131)
at
org.apache.catalina.connector.Connector.initInternal(Connector.java:1025)
at
org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:122)
at
org.apache.catalina.core.StandardService.initInternal(StandardService.java:525)
at
org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:122)
at
org.apache.catalina.core.StandardServer.initInternal(StandardServer.java:986)
at
org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:122)
at org.apache.catalina.startup.Catalina.load(Catalina.java:690)
at org.apache.catalina.startup.Catalina.load(Catalina.java:713)
at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
at
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:569)
at
org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:302)
at
org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:472)
---
Note that we don't use Jigsaw in our application.
You can find in the attachments all the logs we get when starting.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
[Bug 69576] Tomcat doesn't start on JDK 17 due to an ExceptionInInitializerError
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=69576
--- Comment #22 from evelynwang0308@gmail.com ---
(In reply to Thomas F from comment #13)
> When will Tomcat 10.1.36 with this critical fix be released?
>
> This website:
> https://versionlog.com/apache-tomcat/10.1/ https://grade-calculator.io/
> claims that it was already released on 2/13, but it's not here:
> https://downloads.apache.org/tomcat/tomcat-10/
> That URL, which only carries the latest release, is still showing 10.1.35
> Also, the changelog URL:
> https://tomcat.apache.org/tomcat-10.1-doc/changelog.html
> Is showing 10.1.35 as the latest.
The fix for this issue is included in Tomcat 10.1.36, which is currently in the
release pipeline. The release process sometimes takes a few extra days for
final verification and mirror synchronization. Hang tight - the fixed version
should be available soon!
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
[Bug 69576] Tomcat doesn't start on JDK 17 due to an ExceptionInInitializerError
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=69576
--- Comment #14 from Chuck Caldarale <n8...@gmail.com> ---
Voting for 10.1.36 has completed, so it will likely be available within the
next day or two.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
[Bug 69576] Tomcat doesn't start on JDK 17 due to an ExceptionInInitializerError
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=69576
Anshu <an...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|FIXED |---
Ever confirmed|1 |0
Status|RESOLVED |UNCONFIRMED
--- Comment #17 from Anshu <an...@gmail.com> ---
The same issue is exist for window os as well, while running the configuration
with 10.1.36 I am still getting the exception as '
Java.lang.illegalStateException:unable to disable the global canonical file
name cache or confirm that it is disabled when starting the web series source
set'
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
[Bug 69576] Tomcat doesn't start on JDK 17 due to an ExceptionInInitializerError
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=69576
Mark Thomas <ma...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|UNCONFIRMED |RESOLVED
--- Comment #18 from Mark Thomas <ma...@apache.org> ---
Yes, you'll need to upgrade. See the 10.1.37 change log.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
[Bug 69576] Tomcat doesn't start on JDK 17 due to an ExceptionInInitializerError
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=69576
Remy Maucherat <re...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |markus.strehle@sap.com
--- Comment #6 from Remy Maucherat <re...@apache.org> ---
*** Bug 69578 has been marked as a duplicate of this bug. ***
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
[Bug 69576] Tomcat doesn't start on JDK 17 due to an ExceptionInInitializerError
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=69576
--- Comment #8 from Remy Maucherat <re...@apache.org> ---
(In reply to Mark Thomas from comment #7)
> (In reply to Remy Maucherat from comment #5)
>
> > The additional catch will be in 11.0.4, 10.1.35 and 9.0.100.
>
> Correction: 10.1.36
Indeed. Are we moving on with a round of new releases to fix this, given that
it has been reported quite a few times already ?
I verified the fix works (removing --add-opens=java.base/java.io=ALL-UNNAMED
from catalina.sh is enough to reproduce with the default server.xml without
running into other side effects).
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
[Bug 69576] Tomcat doesn't start on JDK 17 due to an ExceptionInInitializerError
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=69576
--- Comment #21 from John Harby <fl...@gmail.com> ---
As an alternative I was able to resolve this by adding this to my VM args in my
run configuration:
—add-opens java.base/java.io=ALL-UNNAMED
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
[Bug 69576] Tomcat doesn't start on JDK 17 due to an ExceptionInInitializerError
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=69576
--- Comment #10 from Remy Maucherat <re...@apache.org> ---
Ok, so this should (mostly) not affect standalone, but it's still very
annoying. I would prefer doing a new release after we can reasonably rule out
any other regressions (we seem to be fine so far, so it's 90% likely we're good
enough).
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
[Bug 69576] Tomcat doesn't start on JDK 17 due to an ExceptionInInitializerError
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=69576
--- Comment #7 from Mark Thomas <ma...@apache.org> ---
(In reply to Remy Maucherat from comment #5)
> The additional catch will be in 11.0.4, 10.1.35 and 9.0.100.
Correction: 10.1.36
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
[Bug 69576] Tomcat doesn't start on JDK 17 due to an ExceptionInInitializerError
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=69576
--- Comment #9 from Mark Thomas <ma...@apache.org> ---
(In reply to Remy Maucherat from comment #8)
> Are we moving on with a round of new releases to fix this, given
> that it has been reported quite a few times already ?
I'm happy to do that.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
[Bug 69576] Tomcat doesn't start on JDK 17 due to an ExceptionInInitializerError
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=69576
zeitlinger@gmail.com <ze...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |zeitlinger@gmail.com
--- Comment #3 from zeitlinger@gmail.com <ze...@gmail.com> ---
You can reproduce this issue on
https://github.com/prometheus/client_java/pull/1271
Just do `mvn verify`
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
[Bug 69576] Tomcat doesn't start on JDK 17 due to an ExceptionInInitializerError
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=69576
Anshu <an...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |UNCONFIRMED
Resolution|FIXED |---
--- Comment #19 from Anshu <an...@gmail.com> ---
10.1.37 is not available in artifactory
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
[Bug 69576] Tomcat doesn't start on JDK 17 due to an ExceptionInInitializerError
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=69576
Chuck Caldarale <n8...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|UNCONFIRMED |RESOLVED
--- Comment #20 from Chuck Caldarale <n8...@gmail.com> ---
Stop reopening the BZ report.
The problem was fixed in 10.1.37, and is included in all following 10.1.x
versions, with 10.1.39 being the latest to be released.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
[Bug 69576] Tomcat doesn't start on JDK 17 due to an ExceptionInInitializerError
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=69576
--- Comment #13 from Thomas F <sp...@mailfence.com> ---
When will Tomcat 10.1.36 with this critical fix be released?
This website:
https://versionlog.com/apache-tomcat/10.1/
claims that it was already released on 2/13, but it's not here:
https://downloads.apache.org/tomcat/tomcat-10/
That URL, which only carries the latest release, is still showing 10.1.35
Also, the changelog URL:
https://tomcat.apache.org/tomcat-10.1-doc/changelog.html
Is showing 10.1.35 as the latest.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
[Bug 69576] Tomcat doesn't start on JDK 17 due to an ExceptionInInitializerError
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=69576
Remy Maucherat <re...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #5 from Remy Maucherat <re...@apache.org> ---
(In reply to Einar Bjarni Halldórsson from comment #4)
> Also happens to me after upgrading to Tomcat 11.0.3
>
> OS: FreeBSD 14.2-RELEASE
> JVM: OpenJDK 64-Bit Server VM (build 17.0.13+11-1, mixed mode, sharing)
>
> Fixed by adding to JVM options: "--add-opens=java.base/java.io=ALL-UNNAMED"
Ok so it makes sense.
The additional catch will be in 11.0.4, 10.1.35 and 9.0.100.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
[Bug 69576] Tomcat doesn't start on JDK 17 due to an ExceptionInInitializerError
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=69576
Remy Maucherat <re...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |rgarciapariente@gmail.com
--- Comment #2 from Remy Maucherat <re...@apache.org> ---
*** Bug 69577 has been marked as a duplicate of this bug. ***
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
[Bug 69576] Tomcat doesn't start on JDK 17 due to an ExceptionInInitializerError
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=69576
Mark Thomas <ma...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |gr.grzybek@gmail.com
--- Comment #11 from Mark Thomas <ma...@apache.org> ---
*** Bug 69581 has been marked as a duplicate of this bug. ***
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
[Bug 69576] Tomcat doesn't start on JDK 17 due to an ExceptionInInitializerError
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=69576
Mark Thomas <ma...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |elatllat@gmail.com
--- Comment #12 from Mark Thomas <ma...@apache.org> ---
*** Bug 69582 has been marked as a duplicate of this bug. ***
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
[Bug 69576] Tomcat doesn't start on JDK 17 due to an ExceptionInInitializerError
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=69576
--- Comment #1 from Remy Maucherat <re...@apache.org> ---
I fail to reproduce this error (the error says it is a module access issue, and
the Tomcat scripts open everything; are you trying something more restrictive
?) but the JreCompat is not correct since setAccessible is indeed documented as
throwing some additional runtime exceptions and the intent of the code is to
not fail.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
[Bug 69576] Tomcat doesn't start on JDK 17 due to an ExceptionInInitializerError
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=69576
--- Comment #4 from Einar Bjarni Halldórsson <ei...@isnic.is> ---
Also happens to me after upgrading to Tomcat 11.0.3
OS: FreeBSD 14.2-RELEASE
JVM: OpenJDK 64-Bit Server VM (build 17.0.13+11-1, mixed mode, sharing)
Fixed by adding to JVM options: "--add-opens=java.base/java.io=ALL-UNNAMED"
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
[Bug 69576] Tomcat doesn't start on JDK 17 due to an ExceptionInInitializerError
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=69576
--- Comment #15 from Thomas F <sp...@mailfence.com> ---
Thanks.
I have received reports, however, that the issue is still happening on MacOS:
WARN JreCompat - Failed to set the java.io.FileSystem.useCanonCaches static
field java.lang.IllegalAccessException: class
org.apache.tomcat.util.compat.JreCompat cannot access a member of class
java.io.FileSystem (in module java.base) with modifiers "static final"
at
java.base/jdk.internal.reflect.Reflection.newIllegalAccessException(Reflection.java:392)
at
java.base/java.lang.reflect.AccessibleObject.checkAccess(AccessibleObject.java:674)
at java.base/java.lang.reflect.Field.checkAccess(Field.java:1102)
at java.base/java.lang.reflect.Field.set(Field.java:797)
at
org.apache.tomcat.util.compat.JreCompat.disableCanonCaches(JreCompat.java:326)
at
org.apache.catalina.webresources.DirResourceSet.initInternal(DirResourceSet.java:353)
This is with Java 17 and Tomcat 10.1.36. Note the different exception hit
rather than InaccessibleObjectException. I am not hitting this directly, as I
am on Linux. I am told they installed OpenJDK 17 via homebrew.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
[Bug 69576] Tomcat doesn't start on JDK 17 due to an ExceptionInInitializerError
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=69576
--- Comment #16 from Mark Thomas <ma...@apache.org> ---
Yes, I am working on further improvements for MacOS and Linux.
One possible workaround is to add
<Resources readOnly="true" />
to the <Context> element in CATALINA_BASE/conf/context.xml
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org