metadata-support - [Metadata-Support] Re: [InCommon NOTICE] How to Protect Against Failed Metadata Processes [ACTION REQUIRED]
Subject: InCommon metadata support
List archive
[Metadata-Support] Re: [InCommon NOTICE] How to Protect Against Failed Metadata Processes [ACTION REQUIRED]
Chronological Thread
- From: David Gersic <>
- To: "" <>
- Subject: [Metadata-Support] Re: [InCommon NOTICE] How to Protect Against Failed Metadata Processes [ACTION REQUIRED]
- Date: Tue, 22 Sep 2015 13:41:06 +0000
- Accept-language: en-US
- Authentication-results: spf=none (sender IP is ) ;
- Spamdiagnosticmetadata: NSPM
- Spamdiagnosticoutput: 1:23
Hi Tom,
A suggestion for this page: how to detect fail(ing) metadata updates. A
simple paragraph on what to look for, how would I know if I'm affected by
this, that kind of thing. I think it's as simple as checking to see that the
file is updated and that the expiration date in the file is changing
appropriately.
It would also be helpful if, sometime between now and the 2016 import of
EduGAIN data, you could publish a test metadata URL so that IdP owners can
try it to see if it works before it goes live. I'm hoping that the EduGAIN
metadata will be first published to
(http://md.incommon.org/InCommon/InCommon-metadata-preview.xml) with an
announcement.
________________________________________
From:
<>
on behalf of Tom Scavo
<>
Sent: Tuesday, September 22, 2015 7:24 AM
To:
Subject: [InCommon NOTICE] How to Protect Against Failed Metadata Processes
[ACTION REQUIRED]
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
- [Metadata-Support] Re: [InCommon NOTICE] How to Protect Against Failed Metadata Processes [ACTION REQUIRED], David Gersic, 09/22/2015
- Re: [Metadata-Support] Re: [InCommon NOTICE] How to Protect Against Failed Metadata Processes [ACTION REQUIRED], Tom Scavo, 09/22/2015
- Re: [Metadata-Support] Re: [InCommon NOTICE] How to Protect Against Failed Metadata Processes [ACTION REQUIRED], Tom Scavo, 09/22/2015
Archive powered by MHonArc 2.6.16.