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.

UIMAPI not reliable. API calls succeed then fail with 500 error.

book

Article ID: 186529

calendar_today

Updated On:

Products

NIMSOFT PROBES DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

On some requests, uimapi works, then fails, then works, then fails again when using the same REST call/request. The failures show-> Error 500 - The session was closed by the remote host. This happens for some servers and probes but not all.

Same results when the URL is provided to a browser, like this one:
http://usxxxxxxxx00v/uimapi/probes/xxx_GLOBAL_PROD/EXE_EXT_PRI/xxxxx21as34/logmon/config

Also, same results when using the UIM REST API:
https://usxxxxxxxx02v/rest/probe/xxx_GLOBAL_PROD/EXE_EXT_PRI/xxxxx21as34/logmon/config

Cause

- Unknown, most likely a network routing/filtering or Load Balancing issue

Environment

Release : 9.1.0

Component : uimapi

UIM v9.02 or higher

Resolution

1. Set the wasp.log on the Primary hub to loglevel 5 and logsize 20000.

2. Deploy the uimapi package to the Primary hub.

3. Access the uimapi

     http://<hostname>:<port>/uimapi/docs/index.html

Doc reference:
https://techdocs.broadcom.com/content/broadcom/techdocs/us/en/ca-enterprise-software/it-operations-management/ca-unified-infrastructure-management-probes/GA/probe-development-tools/restful-web-services/uimapi-apis.html

4. Configure/click on the api call you'd like to test

5. Use "Try it out" button and examine the resultant status code

6. If there are any issues, use your browsers development tools, e.g., F12 (Network) to examine the response/response codes, and check the wasp.log on the Primary as well. You may also choose to check the traffic using a wireshark trace.

In this case, the uimapi response was fine but in the customer's network, it appears that either there is some network/filtering issue or traffic is going through a Loadbalancer and thus the uimapi fails/succeeds on each successive api call. This was NOT reproducible in the lab.

Moreover, when tested on the customer's 'Test' systems, it could not be reproduced.