Windows 11 pro - problem launching Jetty with ${jetty.home}\etc\jetty-ee10-deploy.xml <Configure> (or next one ?) #11270
Assignees
Labels
Milestone
Comments
|
This reads like an XML entity resolver issue. |
|
I am unable to replicate. I'm going to need more information. First thing I noticed in your description, what's in your Can you run
|
joakime
added
More Info Required
Unable To Replicate
Microsoft Windows
|
The error This is the opening of a typical XML file in Jetty 12. <?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE Configure PUBLIC "-//Jetty//Configure//EN" "https://eclipse.dev/jetty/configure_10_0.dtd">
<Configure id="Server" class="org.eclipse.jetty.server.Server">Note that the URL has changed over the years. See: https://github.com/jetty/jetty.project/blob/jetty-12.0.5/jetty-core/jetty-xml/src/main/resources/org/eclipse/jetty/xml/catalog-configure.xml (and the various |
|
Hi !
Weird ? What means the "source=Deprecated" ? |
|
I added "own" xml one by one and faced Due to Jetty 9 xml in jetty base I tried to migrate to Jetty 12 |
|
Here is the full log with --debug |
|
What are the contents of your |
|
Sorry, was off |
|
Copied from your XML <Set name="handler">
<New id="Handlers" class="org.eclipse.jetty.server.handler.HandlerCollection">
<Set name="handlers">
<Array type="org.eclipse.jetty.server.Handler">
<Item>
<New id="Contexts" class="org.eclipse.jetty.server.handler.ContextHandlerCollection"/>
</Item>
<Item>
<New id="DefaultHandler" class="org.eclipse.jetty.server.handler.DefaultHandler"/>
</Item>
</Array>
</Set>
</New>
</Set>Some of these handler classes do not exist in Jetty 12. In fact, delete these two files from your jetty.base Your copy of If you need to tweak something in the default jetty.xml, you either do that entirely with properties in your Example of a tweak.xml ...
<!DOCTYPE Configure PUBLIC "-//Jetty//Configure//EN"
"http://www.eclipse.org/jetty/configure_10_0.dtd">
<!-- Tweak SsslContextFactory Includes / Excludes -->
<Configure id="sslContextFactory" class="org.eclipse.jetty.util.ssl.SslContextFactory$Server">
<!-- Mitigate SLOTH Attack -->
<Call name="addExcludeCipherSuites">
<Arg>
<Array type="String">
<Item>.*_RSA_.*SHA1$</Item>
<Item>.*_RSA_.*SHA$</Item>
<Item>.*_RSA_.*MD5$</Item>
</Array>
</Arg>
</Call>
</Configure> |
|
Ok I'll try thanks I checked why I has to "overwrite" this jetty.xml it was because of
I'll try without them and try to remember why I had to increase this headerCacheSize ... 5 years ago ... sigh |
|
Just use |
|
Thanks, working better. Remark: while parsing an XML with an error, I think Jetty should trace also the faulty xml. It's not always printed in error logs. Question: in my jetty-deploy.xml, I asked to also "hot scan/deploy" for new WARs. This part doesn't work now with Jetty 12. In the doc, I read I have to put with Jetty 12 a somewhere. But, where ? |
Great!
If Jetty is able to, it does that. You even saw that in your #11270 (comment)
This was pointed out in #11270 (comment) |
|
Opened PR #11345 |
|
Thanks, for your help, closing Now trying to correct problem on |
sbordet
added a commit
that referenced
this issue
Feb 27, 2024
…n during error (#11345) Now catching and rethrowing XmlConfigurationException with details about the XML file location. Signed-off-by: Simone Bordet <simone.bordet@gmail.com> Co-authored-by: Simone Bordet <simone.bordet@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I was trying to migrate a Jetty 9 project to Jetty 12.
Windows is up to date, so are most programs.
Jetty version(s)
12.0.5
Jetty Environment
Java version/vendor
(use: java -version)Tested with java 17 and 21
OS type/version
Description
Launching Jetty failed. I extracted Jetty from the ZIP or TGZ from Official site: https://eclipse.dev/jetty/download.php
And didn't modify the {jetty.home}.
I checked the
jetty-ee10-deploy.xmlin XML validators or in Hex editor (to find weird characters).But it's perhaps the next one ? But not in the logs
Error:
How to reproduce?
Launch Jetty
java -jar %JETTY_HOME%/start.jar %JETTY_OPTIONS% %JETTY_STOP_OPTIONS% --module=extThe text was updated successfully, but these errors were encountered: