OI Connector Stops Sending Data Due to Memory Constraints

Products

• Network Observability
• CA Performance Management
• DX Operational Intelligence
• DX Operational Observability

Issue/Introduction

This article describes the resolution for when the NetOps OI Connector stops sending inventory or metrics to DX Operational Intelligence (OI). This issue is often characterized by the OI Connector service stopping unexpectedly or failing to process inventory queries, potentially reporting an "OpenAPI Inventory Query Failed with Status: 400" error in the logs.

Environment

• DX NetOps Performance Management (all supported versions)
• DX Operational Intelligence (OI)

Cause

The default memory allocation for the OI Connector is often insufficient for large environments. When the connector attempts to process extensive inventory or metrics data, it exhausts the available heap space, leading to processing failures or service stops.

Resolution

To resolve these issues, follow these steps to increase the maximum memory allocation and adjust the connection request size:

1. Adjust Java Memory:

   • Navigate to the OI Connector installation directory.
   • Open the wrapper.conf file (typically located in $OIConnector/conf/wrapper.conf) using a text editor.
   • Locate the parameter wrapper.java.maxmemory.
   • Increase the value to an appropriate size based on your environment (e.g., wrapper.java.maxmemory=24576 for 24GB).

2. Adjust OData Request Size:

   • Navigate to the OI Connector conf directory.
   • Open the java.conf file using a text editor.
   • Add or modify the following parameter to increase the allowed remote connection size: -Dremote.connection.maxSize=262144000

3. Restart the Service:

   • Restart the OI Connector service for the changes to take effect.