ResolverExceptions ignored in AbstractReloadingMetadataResolver.RefreshMetadataTask

[Josu Vergara]

Hi Brent and Scott,

Thanks a lot for the quick answer.  Our goal is to be able to inform our 
administrator through our own logs that a problem occurred with the 
metadata source.  We considered the possibility of filtering the logs 
and in the meantime and that is what we plan to implement.  However we 
prefer to use a public interface rather than having a solution based on 
the content of a logged message.

I have created the following Jira ticket: 
https://issues.shibboleth.net/jira/browse/OSJ-193

Regards,

Josu


On 02/08/2017 07:52 PM, Cantor, Scott wrote:
> On 2/8/17, 1:52 PM, "dev on behalf of Brent Putman" <dev-bounces at shibboleth.net on behalf of putmanb at georgetown.edu> wrote:
>
>> 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?
> Most of which could be done with logback in response to the log event, it's worth noting.
>
> -- Scott
>
>      
>      
>