Jetty Quickstart with Shib IDP?

[Dylan Martin]

Got it!  It's the random number generator.  It's trying to pull a bunch of
entropy out of /dev/random.  Not sure if there is a way to prime
/dev/random prior to restart, but I did find a way to use /dev/urandom,
which is:

-Djava.security.egd=file:/dev/urandom

added to startup script.



On Tue, Nov 15, 2016 at 12:31 PM, Brent Putman <putmanb at georgetown.edu>
wrote:

>
>
> On 11/15/16 2:59 PM, Cantor, Scott wrote:
>
> It takes a few minutes.  Is that not considered a long time?
>
> Mine takes 5 seconds to start initializing and finishes loading metadata after 20. Whatever your issue is, it's envirommental.
>
>
> I would agree that it's environmental.  And if the pause is happening
> during the IdP startup itself, as in 3 minute delay logged in
> idp-process.log, then I'm pretty sure the Jetty quickstart stuff you
> originally mentioned will have zero effect on that.  The Jetty and Tomcat
> start time issues are related to things like jar scanning and annotation
> processing, which you can either disable or optimize via configuration if
> you aren't making use of those servlet 3.0 features.  Your issue would
> instead seem to be something affecting the IdP application itself.
>
> --
> To unsubscribe from this list send an email to
> users-unsubscribe at shibboleth.net
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20161121/75a09d92/attachment.html>