IDPv3 seems to fail to reload configuration when under heavy load.

[Peter Schober]

* alex.samuseu <alexander.samuseu at gmail.com> [2019-03-01 22:05]:
> A few specialists responsible for some of the setups reported that IDP often
> won't reload updated configuration from disk for hours, sometimes for days -
> until finally they have to restart its service (basically, this means
> terminating the JVM where it runs, and starting it again). A few cases I'm
> aware of are seem to be about reloading metadata of a new SP - until they
> restart the service, they get the standard "The application you have
> accessed is not registered for use with this service" error page which is
> shown when metadata for a certain SP isn't yet known to IDP.

What Rod said.

I.e., I never changed anything to have config files reload
periodically "just in case", instead I reload specific components
(e.g. the resolver or filter) using the provided script iff specific
changes require a reload of said component(s).
Also, all my individual MetadataProviders are set to reload, so again
I never changed service reloading in order to get updated metadata
into the IDP. Works fine with several thousand entities in metadata.

-peter