Clarity: Unable to start the Clarity application


Article ID: 48935


Updated On:


CLARITY PPM FOR ITG CLARITY PPM FEDERAL CA Identity Manager CA Identity Governance CA Identity Portal Clarity PPM SaaS Clarity PPM On Premise



Http Status error 500 is received when trying to login into Clarity. The app-niku.log shows the following error messages:-

 	ERROR YYY-MM-DD HH:MM:SS,999 [WrapperStartStopAppMain] niku.union (none:none:none) Clarity failed to initialize. 	
 	com.niku.union.config.ConfigurationException: Messenger init failed. This could be due to an incorrect 'preferIpv4Stack' setting that is currently set to 'true'. 	
 	Caused by: org.jgroups.ChannelException: failed to start protocol stack 	
 	Caused by: java.lang.Exception: exception caused by UDP.start() 	
 	Caused by: java.lang.Exception: problem creating sockets (bind_addr=/999.999.999.999, mcast_addr=null) 

Steps to Reproduce:

  1. Start Clarity Application Services

  2. Launch Clarity application via the Browser

Expected Results: Clarity login screen appears

Actual Results: Http Status error 500 appears


Review the Clarity System Administration (CSA) Properties and ensure the Bind address value is set correctly. Restart all Clarity Services.

Reference TEC511524 : Clarity: Fact Sheet: Clarity Beacon with Multicasting - include FAQs

Keywords: CLARITYKB, Messenger init failed, failed to initialize, preferIpv4Stack, multi-cast, multicasting.


Release: ESPCLA99000-12.1-Clarity-Extended Support Plus