oi_connector error while getting the ci information from database. java.lang.NullPointerException

Products

• DX SaaS
• CA Unified Infrastructure Management On-Premise (Nimsoft / UIM)
• CA Unified Infrastructure Management SaaS (Nimsoft / UIM)
• DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

The oi_connector probe version 2.02 is experiencing errors and is unable to send metrics:

Jun 27 18:39:12:321 [QOS_PROCESSOR_THREAD-24, oi_connector] Error while getting the ci information from database. java.lang.NullPointerException
 at com.nimsoft.probe.gateway.oi_connector.AbstractObjectPool.releaseObject(AbstractObjectPool.java:89)
 at com.nimsoft.probe.gateway.oi_connector.jdbc.QueryExecutor.executeRdbmsQuery(QueryExecutor.java:160)
 at com.nimsoft.probe.gateway.oi_connector.dao.impl.DBCIDaoImpl.getCiInformationByMetIdSet(DBCIDaoImpl.java:254)
 at com.nimsoft.probe.gateway.oi_connector.processor.QosEventProcessorNASS.getCiInformationFromDB(QosEventProcessorNASS.java:139)
 at com.nimsoft.probe.gateway.oi_connector.processor.QosEventProcessorNASS.call(QosEventProcessorNASS.java:66)
 at com.nimsoft.probe.gateway.oi_connector.processor.QosEventProcessorNASS.call(QosEventProcessorNASS.java:36)
 at java.util.concurrent.FutureTask.run(FutureTask.java:266)
 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
 at java.lang.Thread.run(Thread.java:750)

Environment

• DX SaaS
• DX O2
• UIM
• oi_connector 2.01, 2.02 or higher
• apm_bridge 2.01

Cause

• configuration

Resolution

1. The oi_connector must be on a robot connected to/under the Primary hub but not on the Primary hub robot itself.
   
   If it is on Primary Hub, then please establish and use a dedicated robot for both the oi_connector and apm_bridge and deactivate the oi_connector on the Primary.

Here are the steps required to install the oi_connector on a robot under the hub:

For an OI Connector instance deployed on a remote robot machine connected to the primary hub the foillowing keys must be set:

• • data_engine_address
  • primary_hub_address
  • connect_to_primary_hub

The values of the following parameters can be set from Infrastructure Manager -> Setup -> Raw Configure. To do so, deactivate if the running probe is running, set the parameter values, and activate the probe again.

For example:

data_engine_address = /<domain_name>/ <primary_hub_name>/<primary_robotname>/data_engine

primary_hub_address = /<domain_name>/ <primary_hub_name>/<primary_robotname>/hub

connect_to_primary_hub = true

2. Please add the following key and value:

skip_second_pass_ci_fetch = true

The keys listed below should alreay be present and set in the oi_connector but its good to double-check.

get_ci_details_alive_time_days = 30
qos_bulk_size = 5000
qos_payload_bulk_size = 1000
get_ci_details_by_met_id_list = true

     3. This parameter needs to be set to false.

enable_alive_time_batches = false

loglevel = 1 

After following the steps above, if the issue persists please attach the oi_connector.log and apm_bridge.log and data_engine.log to the case.

Issues/errors resolved for this particular case/scenario.