<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p><br>
</p>
<br>
<div class="moz-cite-prefix">On 2/8/17 3:58 AM, Josu Vergara wrote:<br>
</div>
<blockquote
cite="mid:d2bc5e2e-9cd4-7493-3d72-e36356f119da@adnovum.ch"
type="cite">
<meta http-equiv="content-type" content="text/html;
charset=windows-1252">
<p>Hi,</p>
<p>When there is a problem retrieving the metadata after the
initial refresh, the <font face="Courier New, Courier,
monospace">ResolverException</font> are silently ignored in
the code of <font face="Courier New, Courier, monospace">AbstractReloadingMetadataResolver.RefreshMetadataTask</font>.</p>
</blockquote>
<br>
Well, they aren't *silently* ignored. The refresh() that is called
from the task catches all Throwable, and logs the error.<br>
<br>
<br>
<blockquote
cite="mid:d2bc5e2e-9cd4-7493-3d72-e36356f119da@adnovum.ch"
type="cite">
<p> Even though the different implementations of <font
face="Courier New, Courier, monospace">AbstractReloadingMetadataResolver</font>
log error messages before generating the <font face="Courier
New, Courier, monospace">ResolverException</font> </p>
</blockquote>
<br>
Yes, but it's not just the different concrete subclass impls, the
AbstractReloadingMetadataResolver itself logs all exceptions raised
and visible in the the refresh().<br>
<br>
<br>
<blockquote
cite="mid:d2bc5e2e-9cd4-7493-3d72-e36356f119da@adnovum.ch"
type="cite">
<p>it would be great if we could have a mechanism to be notified
in the code that an error occurred (for instance using a
Listener pattern). Is this a known limitation? Are there plans
to implement a solution?<br>
</p>
</blockquote>
<br>
I suppose it was "known", in that there is a comment there in the
catch block that nothing further is to be done. No, there aren't
any existing plans to change anything at this time. That's because
OpenSAML is primarily driven by the needs of the Shib IdP, and we
just don't have a use case for it.<br>
<br>
That said, it wouldn't be hard to add an error listener capability
to it. If you want to open a Jira ticket, that's fine, and we'll
consider it.<br>
<br>
Just curious: what would you do in such a listener - fire an email
to an administrator; trigger an event to a management system (SNMP,
etc); actually do something to attempt another refresh before the
next scheduled one; or other?<br>
<br>
</body>
</html>