Since when is a container restart required to refresh DS Metadata?

[Cantor, Scott]

On 9/14/11 3:29 PM, "Dan McLaughlin" <dmclaughlin at tech-consortium.com>
wrote:

>I have a very plain configuration using DS 1.1.2 on Tomcat (see
>wayfconfig.xml below).  If I change the metadata, the only way I can
>get it to immediately update is to bounce the entire container.
>Restarting just the Discovery Service web application doesn't even
>work.

Restarting web apps basically doesn't work reliably. Not with thie code
anyway, and not with Tomcat.

>I do see the following message in the DS logs: ...next refresh will
>occur at approximately 2011-09-14T20:45:34.386Z  But I don't
>particularly want to wait that long our bounce the container.

That would be a different question. The example I was using has the same
kind of logging output, and we haven't tried to force more frequent
reloads.

>There's
>got to be a way to tell the DS to check the metadata for changes more
>often, I just haven't found it yet.  What be nice is a JMX MBean I
>could poke.

The intent is to reuse the IdP's existing code. But the config isn't
reused, and I don't know if there's a way now to set the provider options
to control the interval. I think that's TBD.

But the IdP does not support "instant" reloads on file changes, it's
interval-based. Therefore this code won't either.

-- Scott