...
https://wiki.shibboleth.net/confluence/display/IDP30/Jetty93
https://wiki.shibboleth.net/confluence/display/IDP30/Jetty92
https://wiki.shibboleth.net/confluence/display/IDP30/ApacheTomcat8
https://wiki.shibboleth.net/confluence/display/SHIB2/IdpGlassfishPrepare
https://wiki.shibboleth.net/confluence/display/SHIB2/IdPApacheTomcatPrepare
https://wiki.shibboleth.net/confluence/display/SHIB2/IdPJetty7Prepare
https://wiki.shibboleth.net/confluence/display/SHIB2/IdPJetty9Prepare
| Tip | ||
|---|---|---|
| ||
| Currently the InCommon metadata aggregate is ~32MB (and growing) so Shibboleth IdP deployers in the InCommon Federation should plan to reconfigure their Java container as recommended by the Shibboleth Project. |
...
| Tip | ||
|---|---|---|
| ||
| As a precaution, it is recommended that deployers allocate at least 1500MB of heap space in the JVM as soon as possible. Do this for all your Shibboleth IdP deployments, in both test and production, for both V3 and V2. |
For some Shibboleth IdP deployments, even that may not be enough. The following advice was overheard on the Shibboleth mailing list:
Use a 64-bit OS, hand it 3G or more, and stop wasting valuable person time trying to save money on RAM.
Please take this issue very seriously!
Working Around a Known Logging Issue
...