...
All Shibboleth IdP deployers in the InCommon Federation are strongly advised to take the following precautions to protect themselves against possible failed metadata processes:
Allocate at least 1024MB 1500MB of heap space in the JVM
Enable DEBUG-level logging on the following Java classes:
V2: org.opensaml.saml2.metadata.provider.AbstractReloadingMetadataProvider
V3: org.opensaml.saml.metadata.resolver.impl.AbstractReloadingMetadataResolver
...
Heap Allocation in the JVM
As of September 17February 18, 20152016, the Shibboleth Project recommends at least 1024MB 1500MB of heap space for deployments that rely on metadata files larger than 25MB. This recommendation applies to both Shibboleth IdP V3 and Shibboleth IdP V2:
...
| Tip | ||
|---|---|---|
| ||
| Currently the InCommon metadata aggregate is ~16MB. When we start importing eduGAIN metadata early in 2016, the aggregate will grow to ~32MB. In preparation for eduGAIN, ~32MB and 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 1024MB 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. |
...