To answer my own problem. Turned out that downgrading to java 1.5 fixes
the problem. The basic IdP software runs fine with 1.6 (installed by
default on our servers) but not hashib.
For those interested diagnosis was assisted by changing the default
logging to log4j in idp.xml which gives more diagnostics. The problem
seems to lie with the jgroups.jar code used to replicate between servers
in hashib. Perhaps the hashib code needs to be revisited?
Colin.
On 7 Jul, Colin Farrow wrote:
> I have a working IdP which I am attempting to upgrade with HAshib.
> Deployment of HAshib successfully creates a new shibboleth-idp.war and
> tomcat installs this without errors and the IdP also works at this point.
> However as soon as I modify the configuration in etc/idp.xml to use the
> Hashib extensions I get a 404 Not Found after authentication and the
> following error message in shib-error.log and the IdP fails to start.
>
> Failed to instantiate a Name Identifier Mapping:
> java.lang.reflect.InvocationTargetException:edu.internet2.middleware.shibboleth.common.NameIdentifierMappingException:
> Unable to configure or start Handle mapping replication service: Unable to
> start data replication service.
>
> If I create a deliberate error in the HAshib configuration
> (cache-config.xml) then I get an error in configuration as one might
> expect.
>
> Has any one seen the above error or know how I can diagnose this or know
> someone who can help?
>
> Thanks, Colin.
--
Colin Farrow
Computing Service, University of Glasgow, Glasgow G12 8QQ
Tel: 0141 330 4862, Email: [log in to unmask]
---
|