Where is java_home detected from by the installer?

[Dave Perry]

Hi Jon

I was told that there was more Jetty experience amongst the UKF staff - so it was better to go with that.
I also get the sense it is preferred by the main Shibboleth people from various threads I've seen on this mailing list, and as my team has no need for java on any other system sticking to one thing that we can get support for more easily made sense.

I'll look at the boot order, the idea crossed my mind too.

There is a strange error I get from the logs, when it wasn't responding to status.sh or version.sh and I restart it you get the following when it tries to shut the service down (this from idp-process.log):

2017-07-17 13:35:48,875 - INFO [net.shibboleth.utilities.java.support.service.AbstractReloadableService:207] - Service 'shibboleth.LoggingService': Starting shutdown
2017-07-17 13:35:48,876 - INFO [net.shibboleth.utilities.java.support.service.AbstractReloadableService:216] - Service 'shibboleth.LoggingService': Completing shutdown
2017-07-17 13:35:48,899 - ERROR [org.springframework.web.context.ContextLoader:351] - Context initialization failed
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'shibboleth.metrics.RegisterMetricSets$child#0' defined in file [/opt/shibboleth-idp/system/conf/../../conf/admin/metrics.xml]: Cannot resolve reference to bean 'shibboleth.metrics.AttributeResolverGaugeSet' while setting bean property 'arguments' with key [7]; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'shibboleth.metrics.AttributeResolverGaugeSet' defined in file [/opt/shibboleth-idp/system/conf/general-admin-system.xml]: Invocation of init method failed; nested exception is net.shibboleth.utilities.java.support.component.ComponentInitializationException: Injected service was null or not an AttributeResolver
	at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:359)
Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'shibboleth.metrics.AttributeResolverGaugeSet' defined in file [/opt/shibboleth-idp/system/conf/general-admin-system.xml]: Invocation of init method failed; nested exception is net.shibboleth.utilities.java.support.component.ComponentInitializationException: Injected service was null or not an AttributeResolver
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1578)
Caused by: net.shibboleth.utilities.java.support.component.ComponentInitializationException: Injected service was null or not an AttributeResolver
	at net.shibboleth.idp.attribute.resolver.impl.AttributeResolverServiceGaugeSet.doInitialize(AttributeResolverServiceGaugeSet.java:104)

If that makes sense to anyone, as to why it wobbled?

Thanks,
Dave

_________________________________________________
Dave Perry
eLearning Technologist, Hull College Group (Monday – Thursday)

Room L34 - Queens Gardens Library
Wilberforce Drive, Queen's Gardens, Hull, HU1 3DG
Extension 2230 / Direct Dial 01482 381930

* Need a fast reply? Try elearning at hull-college.ac.uk *


-----Original Message-----
From: Jon Agland [mailto:Jon.Agland at jisc.ac.uk] 
Sent: 17 July 2017 14:33
To: users at shibboleth.net; Dave Perry
Subject: Re: Where is java_home detected from by the installer?

> We ditched Tomcat as your team said Jetty was better supported by
> you!
> I didn't put Jetty 9.4 as part of the upgrade as it's not mentioned
> as Supported on the wiki.

So the Shibboleth project Wiki says says that the "recommended
container implementation is Jetty", but it also says that "Only Tomcat
8+ and Jetty 9.2+ are officially supported by the project at this
time", so as I see it either are valid, and I'm hoping that's what we
(assuming you meant UK federation) would have advised.

https://wiki.shibboleth.net/confluence/display/IDP30/SystemRequirements

The two systems I managed to lay my hands on easiest were running
Tomcat.


> I did run those commands you suggested manually (vs editing
> /etc/profile.local again), and it's let me run the installer and
> passes version/status checks.
> Adding that java.sh as suggested to the folder you specified is also
> working post-reboot.

Great to hear it's working :)

> 
> So thanks for your help.
> 
> I notice that on reboot the first load of the IdP is unsuccessful
> (restarting jetty does the trick), but I don't know if that's a jetty
> or java thing (I'll have to investigate at some point).

Off the top of my head.. check your logs, it could be the order that
services are loading on system startup?

Cheers,

Jon

**********************************************************************
This message is sent in confidence for the addressee
only. It may  contain confidential or sensitive
information.  The contents are not to be disclosed
to anyone other than the addressee.  Unauthorised
recipients are requested to preserve this
confidentiality and to advise us of any errors in
transmission.  Any views expressed in this message
are solely the views of the individual and do not
represent the views of the College.  Nothing in this
message should be construed as creating a contract.

Hull College Group owns the email infrastructure, including the contents.

Hull College Group is committed to sustainability, please reflect before printing this email.
**********************************************************************

TEXT