Policy_management queue queuing up with HTTP 500 errors after UIM 23.4.8 upgrade

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

After upgrading to UIM 23.4.8, the policy_management queue on the primary hub remains yellow and queues up without processing data.

Symptoms:

• The policy_management_ws.log on the OC capture the following: Registration of this policy node to master failed, java.lang.RuntimeException: Failed : HTTP error code : 500
• The wasp log on the Primary hub capture the following java.lang.IllegalArgumentException: java.lang.IllegalArgumentException: Invalid contextPath '/adminconsoleapp/api': must match the start of requestPath: '/adminconsoleapp//api/amIPrimary/policy_processor'

Environment

• DX Unified Infrastructure Management (UIM) 23.4.8
• Operator Console (OC) with wasp probe

Cause

A trailing slash (/) in the controller_url configured within the OC wasp probe's raw configuration (policy_management_ws) causes the request path to be constructed with a double slash (e.g., /adminconsoleapp//api/...). The Spring Framework on the primary hub enforces strict request path validation and rejects the request, resulting in an HTTP 500 Internal Server Error.

Resolution

To resolve this, perform the following steps on all Operator Console (OC) servers in the environment:

1. Open the Raw Configuration for the wasp probe on the OC server.
2. Navigate to the following path: webapps > policy_management_ws > custom > uncrypted
3. Locate the key: controller_url
4. Modify the value to remove the trailing slash:
   • Incorrect: http://<hostname>/adminconsoleapp/
   • Correct: http://<hostname>/adminconsoleapp
5. Deactivate and reactivate the wasp probe on the OC server.
6. Repeat these steps for every OC server in your deployment.
7. Once updated on all servers, verify the policy_management queue on the primary hub. It should reconnect and turn green as it begins processing data.