[JIRA] Resolved: (JOST-168) File-based metadata provider often fails to detect changed file
Scott Cantor (JIRA)
noreply at shibboleth.net
Thu Aug 25 19:50:26 BST 2011
[ https://issues.shibboleth.net/jira/browse/JOST-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Scott Cantor resolved JOST-168.
-------------------------------
Resolution: Invalid
Figured it out, it's a quirk of the workflow I was using to move the changes over.
> File-based metadata provider often fails to detect changed file
> ---------------------------------------------------------------
>
> Key: JOST-168
> URL: https://issues.shibboleth.net/jira/browse/JOST-168
> Project: OpenSAML 2 - Java
> Issue Type: Bug
> Components: SAML 2
> Affects Versions: 2.5.1
> Environment: Jetty7.4.2, IdPV 2.3.2
> Reporter: Scott Cantor
> Assignee: Chad La Joie
>
> The FilesystemMetadataProvider seems to have issues detecting changes and often misses them. I'm using a 15m interval right now and I'm getting inconsistent results, with a lot of changes ignored. No apparent pattern yet.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the commits
mailing list