<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;">
<div>Hi All,</div>
<div><br>
</div>
<div>We currently have our relying-party.xml configured to poll for changes. We rarely make changes to our file except for times when we need to add a new RelyingParty for SP’s that don’t support encrypted asserts. We never had a problem with this until recently
when we tried to add a new one for the SP Zoom. When the IdP reloads the file the CPU spikes to 100% and eventually we have to kill tomcat. The configuration is below</div>
<div>
<div> </div>
<div> <rp:RelyingParty id="ucla.zoom.us"</div>
<div> provider="https://shbqa.ais.ucla.edu/idp/shibboleth"</div>
<div> defaultAuthenticationMethod="urn:oasis:names:tc:SAML:2.0:ac:classes:PasswordProtectedTransport"</div>
<div> defaultSigningCredentialRef="IdPCredential"></div>
<div> <rp:ProfileConfiguration xsi:type="saml:SAML2SSOProfile"</div>
<div> signResponses="never"</div>
<div> signAssertions="always"</div>
<div> encryptNameIds="never"</div>
<div> encryptAssertions="never"</div>
<div> includeAttributeStatement="true"/></div>
<div> </rp:RelyingParty></div>
</div>
<div> </div>
<div><br>
</div>
<div>I am also attaching the thread dump we took.</div>
<div><br>
</div>
<div>Thanks</div>
<div><br>
</div>
<div>Warren</div>
<div><br>
</div>
</body>
</html>