Unicast clustering on 14.4 MSC000001: StartException Property assignment of initial_hosts in TCPPING could not be assigned
search cancel

Unicast clustering on 14.4 MSC000001: StartException Property assignment of initial_hosts in TCPPING could not be assigned

book

Article ID: 219878

calendar_today

Updated On:

Products

CA Identity Manager CA Identity Suite

Issue/Introduction

We have installed a new IDM 14.4. cluster on two wildfly-15.0.1.Final servers.

We want to use Unicast and we fed the IDM installation script the hostnames of our two servers, server01 and server02.

The IDM installation completes successfully on each server, but when we go to start up via ./standalone.sh we see the following error, and the IDM application fails to deploy:

MSC000001: Failed to start service org.wildfly.clustering.jgroups.channel.ee: org.jboss.msc.service.StartException in service org.wildfly.clustering.jgroups.channel.ee: java.lang.IllegalStateException: java.lang.IllegalArgumentException: java.security.PrivilegedActionException: java.lang.Exception: Property assignment of initial_hosts in TCPPING with original property value server02,server01 and converted to null could not be assigned.

 

Environment

Release : 14.4

Component : IdentityMinder(Identity Manager)

Cause

The inital_hosts under the TCPPING protocol underneath the JGroups subsystem requires the unicast port number to be present after the hostnames and surrounded by square brackets.

Resolution

 

Reinstall IDM using this format for the unicast hosts so that the standalone-full-ha.xml becomes populated correctly:

host[port]

for example...

192.0.2.5[7600]
192.0.2.6[7600]

Additional Information

192.0.2.5[7600],192.0.2.6[7600]