Skip to Content.
Sympa Menu

inc-ops-notifications - [InCommon NOTICE] How to Protect Against Failed Metadata Processes [ACTION REQUIRED]

Subject: InCommon Operations Notifications

List archive

[InCommon NOTICE] How to Protect Against Failed Metadata Processes [ACTION REQUIRED]


Chronological Thread 
  • From: Tom Scavo <>
  • To:
  • Subject: [InCommon NOTICE] How to Protect Against Failed Metadata Processes [ACTION REQUIRED]
  • Date: Tue, 22 Sep 2015 08:24:53 -0400

You are receiving this message because you are a Site Administrator in
the InCommon Federation or have otherwise subscribed to this mailing
list. Your prompt action may be REQUIRED.

Over the past few months, Shibboleth IdP deployers have reported
numerous failed metadata processes. Evidence suggests that
insufficient memory is the cause of these issues. In some cases, the
root cause of the failure is not being logged.

All Shibboleth IdP deployers in the InCommon Federation are strongly
advised to take the following precautions to protect themselves
against possible failed metadata processes:

1) Allocate at least 1024MB of heap space in the JVM

2) Enable DEBUG-level logging on the following Java classes:
V2: org.opensaml.saml2.metadata.provider.AbstractReloadingMetadataProvider
V3: org.opensaml.saml.metadata.resolver.impl.AbstractReloadingMetadataResolver

See this wiki page for details: https://spaces.internet2.edu/x/zgFwBQ

Feel free to add a comment or suggestion to the above wiki page, or
send a question to the metadata-support mailing list:
https://lists.incommon.org/sympa/info/metadata-support

----
InCommon Operations



  • [InCommon NOTICE] How to Protect Against Failed Metadata Processes [ACTION REQUIRED], Tom Scavo, 09/22/2015

Archive powered by MHonArc 2.6.16.

Top of Page