IdP v3: reload-service.sh

[Kirk Turner-Rustin]

I should add that nothing registers in the Shibboleth logs when I run 
reload-service.sh with debug logging enabled for 
net.shibboleth.utilities.java.support.service.AbstractReloadableService 
and net.shibboleth.ext.spring.service.ReloadableSpringService
(although I do get debug entries for both nodes during IdP startup).

Kirk

On Tue, 29 Sep 2015, Kirk Turner-Rustin wrote:

> Greetings, friends:
>
> IdP 3.1.1; Tomcat 7.0; OpenJDK 1.7.0
>
> I apologize in advance for the noise if this (as I suspect) turns out to be 
> trivial.
>
> I run reload-service.sh, e.g.:
>
> $ JAVA_HOME=/usr ./reload-service.sh \
>     -id shibboleth.AttributeResolverService
>
> and, while the script runs to completion without error, the service doesn't 
> reload. Reload in fact doesn't appear to have been attempted based on, e.g., 
> the "last reload attempt" timestamp for the service on the IdP status page.
>
> I've also tried:
>
> $ curl 
> http://localhost/idp/profile/admin/reload-service?id=shibboleth.AttributeResolverService
>
> which exhibits the same (non-)behavior (no error; no reload).
>
> I know that the IdP is responsive on localhost because this works:
>
> $ links http://localhost/idp/status
>
> Might this be an OpenJDK vs Oracle JDK issue?
>
> Many thanks,
> Kirk

-- 
   Kirk Turner-Rustin SCJP  | Senior Systems Analyst
   Ohio Wesleyan University | Information Services
   http://www.owu.edu       | http://infoserv.owu.edu