> Sorry, this case has resolved itself, it was due to the duplication of log4j > settings in the proprietary module and in the Shibboleth IdP. We don't use log4j. Whatever it was was upstream of either error you posted and would have been something low level not loading properly when Spring initialized. -- Scott