Jetty Quickstart with Shib IDP?

[Brent Putman]

On 11/11/16 5:11 PM, Dylan Martin wrote:
> Hi all.  I'm trying to get my IDP to start more quickly.  I'm using
> Jetty 9.3.13 and Shib IDP 3.2.1.  I found the Jetty Quickstart module
> (http://www.eclipse.org/jetty/documentation/9.3.0.v20150612/quickstart-webapp.html)
> and I'm trying to make it work. 

I'm wasn't familiar with that Jetty feature.  Doesn't necessarily sound
like a bad idea, as long as it works, but: Have you looked at the
container logs and the idp-process.log to ascertain exactly why your
IdP's startup is slow in the first place?  I didn't actually think
Jetty's startup was known to be all that slow (compared to newer Tomcat
versions, which is horrible and requires extraordinary measures to
address, see our Tomcat install docs).

I only mention because: One of the biggest/slowest things that the IdP
potentially does at start is to download large batch metadata files via
HTTP (from your federation(s), etc).  When those are sufficiently
large, as they often are with InCommon, etc, that can take quite a long
time.

In IdP 3.3.0, which was just released this week, we added new support
in the batch HTTP metadata resolvers for executing the time-consuming
HTTP fetch in a background thread, if the backup file from a previous
download is available on the filesystem. The backup file is still
loaded in the foreground thread, but that doesn't require any network
ops, so is much faster.  This should usually dramatically reduce the
foreground processing time (i.e. the startup time) when the backup file
is present.  This is enabled by default when using a
FileBackedHTTPMetadataProvider.  This isn't in the wiki docs yet, but
should be there sometime next week.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20161112/ee31cc64/attachment.html>