There are several ways to run XWiki on Jetty:

If you go with the last 2 options, make sure to:

  • Pick a supported version of Jetty.
  • Follow the Jetty setup defined in the xwiki.mod file used for the demo packaging. Note that the default setup used in the Jetty Docker image should work fine out of the box.
  • Since XWiki 14, XWiki works OOB on Jetty 10+. If you're deploying on Jetty 9.4.x, you'll need to edit the WEB-INF/jetty-web.xml file since it currently contains a setup valid for Jetty 10+ and it'll fail in Jetty 9.4. You'll need to add the calls to prependSystemClass and prependServerClass. For example (best is to edit your version so that you can get the latest changes in it):
    <Configure class="org.eclipse.jetty.webapp.WebAppContext">
     <!-- In order to avoid getting a "java.lang.IllegalStateException: Form too large" error when editing large page in
           XWiki we need to tell Jetty to allow for large content since by default it only allows for 20K. We do this by
           passing the "org.eclipse.jetty.server.Request.maxFormContentSize" attribute.
           Note 1: Setting this value too high can leave your server vulnerable to denial of service attacks.
           Note 2: We're setting it here instead of in Jetty's XML configuration files so that the XWiki WAR can be used
           in any Jetty config and work out of the box.
      -->

     <Set name="maxFormContentSize">1000000</Set>
     <!-- Increasing the maxFormKeys in order to be able to import correctly a full wiki (more than 1000 pages in 11.10).
      The import should be fixed at a point to allow importing everything without creating a form with a field by page.
      Once done this configuration can be removed. See https://jira.xwiki.org/browse/XWIKI-11597 for a follow up. -->

     <Set name="maxFormKeys">2000</Set>

     <!-- Tell jetty that javax.mail should be something that is invisible to the user, but if it's provided inside the
           webapp use that instead (this is the case for XWiki). This is needed for work around issue
           https://github.com/appropriate/docker-jetty/issues/108. Note that we don't have this problem in the XWiki
           Standalone packaging since we create a custom distribution of Jetty and we don't include the Jetty "mail"
           module. However we have the problem in our functional Docker-based tests where we use the official Jetty
           image. -->

     <!-- Note: In Jetty 10+ it's no longer necessary to have this hack. Once all the Jetty version we use are >= 10.0
           then we'll be able to remove this file. -->

     <Call name="getSystemClasspathPattern">
       <Call name="add">
         <Arg>-javax.mail.</Arg>
       </Call>
     </Call>
     <Call name="getServerClasspathPattern">
       <Call name="add">
         <Arg>javax.mail.</Arg>
       </Call>
     </Call>

    </Configure>
  • Jetty has introduced a URI Compliance configuration (since 10.0.3+) which, for example, forbids having encoded % characters (encoded as %25%) in URL paths. However XWiki uses these and thus you need to tell Jetty to simply follow the URL RFCs without adding these extra checks. This can be done in several ways:
    • By editing server.ini and adding the line: jetty.httpConfig.uriCompliance=RFC3986
    • If you're using the Jetty Docker image, by passing jetty.httpConfig.uriCompliance=RFC3986 on the docker run command line: docker run ... jetty jetty.httpConfig.uriCompliance=RFC3986.

Docker

  • Extract the XWiki WAR into a directory named xwiki. Let's call this directory [XWIKI_HOME].
  • Run the Jetty Docker image, for example: docker run -v [XWIKI_HOME]:/var/lib/jetty/webapps/xwiki -p 8080:8080 jetty:9-jre11

Manual

  • Download and install Jetty. It's usually as simple as unzipping it in a directory. Let's call this directory [JETTY_HOME].
  • Extract the XWiki WAR into a directory named xwiki in [JETTY_HOME]/webapps/.
  • Open [JETTY_HOME]/webapps/xwiki/WEB-INF/xwiki.properties files and configure a permanent directory
  • (Optional) If you want to modify the port on which Jetty will run, edit [JETTY_HOME]/start.ini. Search for 8080, replace it with the port value you wish to use and uncomment the corresponding property jetty.http.port.

Troubleshooting

Unable to parse form content

In some cases you could obtain one of the following error messages: Unable to parse form content.

More specifically: org.eclipse.jetty.http.BadMessageException: 400: Unable to parse form content.

This can be related to a form containing too many parameters. In order to fix this issue, you can modify your jetty.xml file as explained in Configuring form limits for the server.

Tags:
   

Get Connected