Wasp probe of OC return error "(1) error, Received status (1) on response (for sendRcv) for cmd = 'subscribe' "

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

Wasp probe of OC takes a long time to start and shows the below errors in wasp.log:

Oct 10 18:36:15:110 ERROR [QueueListener.policy_management, com.nimsoft.events.common.notifications.subscribe.AbstractListener] subscribe error: Received status (1) on response (for sendRcv) for cmd = 'subscribe' 
Oct 10 18:36:15:110 ERROR [QueueListener.policy_management, com.nimsoft.events.common.notifications.subscribe.AbstractListener] (1) error, Received status (1) on response (for sendRcv) for cmd = 'subscribe' 

 

 

Environment

Release : All UIM supported versions

Cause

In a load balanced environment with multiple policy_management_ws nodes, the policy_processing should happen in a HA mode.

In order to correctly configure this we have to make some changes to both the primary hub wasp (where Admin Console is hosted) and the OC node wasp(s).

On the primary hub wasp, webapps/adminconsoleapp/custom/uncrypted/ha_mode should be set to HA.

On the OC nodes, all the policy_management_ws nodes should not have policy_processing flag. Then, nodes will be selected dynamically and work in HA mode.

Resolution

Part 1 - In the wasp probe of primary hub

1. Via IM or AC
2. Select the primary hub then raw configure wasp probe
3. Verify the following are set under webapps/adminconsoleapp/custom/uncrypted  (case sensitive)
   ha_mode = HA
   heartbeat_interval_min = 5
   no_failed_attempts = 3
   

 

 

Part2 - In the wasp probe of each OC node

1. Via Im or AC
2. Raw configure wasp
3. Add the following key under webapps/policy_management_ws/custom/uncrypted:

   controller_url = http(s)://<system.domain_name>/adminconsoleapp/
   
   (where system.domain.name is the primary hub e.g. the same URL you use to access admin console)

   

4. Delete the policy_processing key, if it is present in webapps/policy_management_ws/custom/uncrypted

 

 

To confirm that the settings have taken affect:

Monitor the wasp.log for each OC and you will notice the below message in the node that handles the policy processing - meanwhile the error messages in the original description should not be present any longer on any other OC node.

Oct 10 18:39:30:526 WARN  [QueueListener.policy_management, com.nimsoft.events.common.notifications.subscribe.AbstractListener] Establishing connection to queue 'MCS_Profile_Event'. 
Oct 10 18:39:30:526 INFO  [QueueListener.policy_management, com.nimsoft.events.common.notifications.subscribe.AbstractListener] subscribe policy_management to subject: MCS_Profile_Event 

Additional Information

Policy Management in High Availability Mode