Using Jetty 9.2
| Note |
|---|
These pages are examples and do not reflect any normative requirements or assumptions on the part of the IdP software and may be a mix of suggestions from both the project team and deployers. You should take any of this advice with a grain of local salt and consider general security/deployment considerations appropriate to the use of web software in your local environment. The official information about containers and versions we support is solely maintained on the SystemRequirements page. If you wish to operate without complete responsibility for your Java servlet container, you may consider the Windows package we provide that includes an embedded container. |
| Table of Contents |
|---|
The following conventions are used this document:
...
| Code Block | ||||
|---|---|---|---|---|
| ||||
# Required Jetty modules --module=server --module=deploy --module=annotations --module=resources --module=logging --module=requestlog --module=servlets --module=jsp --module=jstl --module=ext --module=plus # Allows setting Java system properties (-Dname=value) # and JVM flags (-X, -XX) in this file # NOTE: spawns child Java process --exec # Uncomment if IdP is installed somewhere other than /opt/shibboleth-idp #-Didp.home=/path/to/shibboleth-idp # Alternate garbage collector that reduces memory needed for larger metadata files -XX:+UseG1GC # Maximum amount of memory that Jetty may use, at least 1.5G is recommended # for handling larger (> 25M) metadata files but you will need to test on # your particular metadata configuration -Xmx1500m # Maximum amount of memory allowed for the JVM permanent generation (Java 7 only) -XX:MaxPermSize=128m |
...