<div dir="ltr">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:<div><br></div><div>-Djava.security.egd=file:/dev/urandom<br></div><div><br></div><div>added to startup script.</div><div><br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Nov 15, 2016 at 12:31 PM, Brent Putman <span dir="ltr"><<a href="mailto:putmanb@georgetown.edu" target="_blank">putmanb@georgetown.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"><span class="">
<p><br>
</p>
<br>
<div class="m_-7734053193155468812moz-cite-prefix">On 11/15/16 2:59 PM, Cantor, Scott
wrote:<br>
</div>
<blockquote type="cite">
<blockquote type="cite">
<pre>It takes a few minutes. Is that not considered a long time?
</pre>
</blockquote>
<pre>Mine takes 5 seconds to start initializing and finishes loading metadata after 20. Whatever your issue is, it's envirommental.</pre>
</blockquote>
<br></span>
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.<br>
</div>
<br>--<br>
To unsubscribe from this list send an email to <a href="mailto:users-unsubscribe@shibboleth.net">users-unsubscribe@shibboleth.<wbr>net</a><br></blockquote></div><br></div>