IDPv3 really slow startup

[Gavin Jackson]

Hi All, 

I have taken the plunge and have just upgraded to IDPv3 (on tomcat 8). 

I am experiencing a very slow start time - in the vicinity of 5-25 minutes! 

I have followed the configuration advice regarding jar scanning on startup but it does not seem to be fixing my problem. 

2015-10-20 10:14:48,130 - INFO [net.shibboleth.idp.log.LogbackLoggingService:240] - Shibboleth IdP Version 3.1.2 
2015-10-20 10:14:48,135 - INFO [net.shibboleth.idp.log.LogbackLoggingService:241] - Java version='1.7.0_79' vendor='Oracle Corporation' 
2015-10-20 10:14:48,137 - INFO [net.shibboleth.utilities.java.support.service.AbstractReloadableService:199] - Service 'shibboleth.LoggingService': Reload time set to: 300000, starting refresh thread 
2015-10-20 10:14:48,189 - INFO [org.opensaml.core.config.InitializationService:48] - Initializing OpenSAML using the Java Services API 
2015-10-20 10:14:49,352 - INFO [org.opensaml.xmlsec.algorithm.AlgorithmRegistry:206] - Algorithm failed runtime support check, will not be usable: http://www.w3.org/2009/xmlenc11#aes128-gcm 
2015-10-20 10:14:49,353 - INFO [org.opensaml.xmlsec.algorithm.AlgorithmRegistry:206] - Algorithm failed runtime support check, will not be usable: http://www.w3.org/2009/xmlenc11#aes192-gcm 
2015-10-20 10:14:49,355 - INFO [org.opensaml.xmlsec.algorithm.AlgorithmRegistry:206] - Algorithm failed runtime support check, will not be usable: http://www.w3.org/2009/xmlenc11#aes256-gcm 
2015-10-20 10:14:49,357 - INFO [org.opensaml.xmlsec.algorithm.AlgorithmRegistry:206] - Algorithm failed runtime support check, will not be usable: http://www.w3.org/2001/04/xmlenc#ripemd160 
2015-10-20 10:14:49,366 - INFO [org.opensaml.xmlsec.algorithm.AlgorithmRegistry:206] - Algorithm failed runtime support check, will not be usable: http://www.w3.org/2001/04/xmldsig-more#hmac-ripemd160 
2015-10-20 10:14:49,371 - INFO [org.opensaml.xmlsec.algorithm.AlgorithmRegistry:206] - Algorithm failed runtime support check, will not be usable: http://www.w3.org/2009/xmlenc11#rsa-oaep 
2015-10-20 10:14:49,377 - INFO [org.opensaml.xmlsec.algorithm.AlgorithmRegistry:206] - Algorithm failed runtime support check, will not be usable: http://www.w3.org/2001/04/xmldsig-more#rsa-ripemd160 
2015-10-20 10:14:49,964 - INFO [net.shibboleth.utilities.java.support.security.BasicKeystoreKeyStrategy:323] - Loading initial default key: secret1 
2015-10-20 10:14:49,999 - INFO [net.shibboleth.utilities.java.support.security.BasicKeystoreKeyStrategy:335] - Default key updated to secret1 
2015-10-20 10:14:50,673 - INFO [net.shibboleth.utilities.java.support.service.AbstractReloadableService:172] - Service 'shibboleth.AttributeFilterService': Performing initial load 
2015-10-20 10:14:50,674 - INFO [net.shibboleth.utilities.java.support.service.AbstractReloadableService:258] - Service 'shibboleth.AttributeFilterService': Reloading service configuration 
2015-10-20 10:14:50,683 - INFO [net.shibboleth.ext.spring.util.SchemaTypeAwareXMLBeanDefinitionReader:317] - Loading XML bean definitions from file [/opt/shibboleth-idp/conf/attribute-filter.xml] 
<<BIG DELAY HERE - 14 minutes>> 
2015-10-20 10:28:34,010 - INFO [net.shibboleth.ext.spring.context.FilesystemGenericApplicationContext:510] - Refreshing ApplicationContext:shibboleth.AttributeFilterService: startup date [ Tue Oct 20 10:28:34 AEDT 2015]; parent: Root WebApplicationContext 
2015-10-20 10:28:34,098 - INFO [net.shibboleth.ext.spring.service.ReloadableSpringService:378] - Service 'shibboleth.AttributeFilterService': Completed reload and swapped in latest configuration for service 'shibboleth.AttributeFilterService' 
2015-10-20 10:28:34,099 - INFO [net.shibboleth.ext.spring.service.ReloadableSpringService:385] - Service 'shibboleth.AttributeFilterService': Reload complete 
2015-10-20 10:28:34,099 - INFO [net.shibboleth.utilities.java.support.service.AbstractReloadableService:199] - Service 'shibboleth.AttributeFilterService': Reload time set to: 900000, starting refresh thread 
2015-10-20 10:28:34,105 - INFO [net.shibboleth.utilities.java.support.service.AbstractReloadableService:172] - Service 'shibboleth.AttributeResolverService': Performing initial load 
2015-10-20 10:28:34,105 - INFO [net.shibboleth.utilities.java.support.service.AbstractReloadableService:258] - Service 'shibboleth.AttributeResolverService': Reloading service configuration 
2015-10-20 10:28:34,114 - INFO [net.shibboleth.ext.spring.util.SchemaTypeAwareXMLBeanDefinitionReader:317] - Loading XML bean definitions from file [/opt/shibboleth-idp/conf/attribute-resolver.xml] 
<<Loads up correctly and login page becomes accessible>> 

Your advise would be greatly appreciated! 

I have tried reducing the check intervals in services.properties but it hasn't made any difference. 

Kind Regards, 
Gavin Jackson 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20151020/0c66c250/attachment-0001.html>