ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Clarity: Error 500 page when trying to access the application. "Messenger init failed. This could be due to an incorrect 'preferIpv4Stack' setting."

book

Article ID: 51450

calendar_today

Updated On:

Products

CA Identity Manager CA Identity Governance CA Identity Portal Clarity PPM SaaS Clarity PPM On Premise

Issue/Introduction

Description:

You get an error 500 page when trying to access Clarity.

In the exception trace, you can find the following message:

"Messenger init failed. This could be due to an incorrect 'preferIpv4Stack' setting that is currently set to 'true'." if you have 'Prefer Ipv4 Stack' checked on NSA,
OR
"Messenger init failed. This could be due to an incorrect 'preferIpv4Stack' setting that is currently set to 'false' ." if you have 'Prefer Ipv4 Stack' unchecked on NSA.

Solution:

This is most likely caused by an incorrect bind address setting.

Please try the following:

  1. On the affected server, log into CSA.

  2. Go to Server Properties, and make sure that the 'Bind Address' it's set up correctly.

    1. If the affected server is part of a Clarity cluster, the 'Bind Address' should be
      server1_ip,server2_ip,server3_ip,...

    2. If the affected server a stand-alone Clarity server, the 'Bind Address' should be the server's IP address.

  3. Save the changes.

  4. Stop, Deploy and Start the Application service, and try to access Clarity.

Environment

Release:
Component: PPMENV
Powered by Wolken Software