Hi,

We have encountered an issue during the Topology Discovery phase of Subsystem registration.

During that process we are sending down requests to the NCMP through the /v1/data endpoint which forwards the request to the ENM Adapter. As we have seen a few of the requests hasn't arrived to the ENM Adapter and we have seen the issues in the NCMP logs:

2024-03-05T16:33:24.019782455+01:00 {"version":"1.2.0","timestamp":"2024-03-05T15:33:24.019+0000","severity":"error","service_id":"eric-oss-ncmp","message":"Async task failed. caused by : java.util.concurrent.TimeoutException","extra_data":{"logger":"org.onap.cps.ncmp.rest.executor.CpsNcmpTaskExecutor","thread_info":{"thread_name":"ForkJoinPool.commonPool-worker-3"}},"metadata":{"pod_name":"eric-oss-ncmp-854cf9f54b-sjbhr","pod_uid":"246eb751-3f35-4d6e-9b22-b662cdeae31e","container_name":"ncmp","node_name":"ceph-n205-vpod2-ceph-n6","namespace":"oss-deploy-b"}} 

We have tried to increase this parameter in the NCMP but even with the increased value we were able to reproduce this issue:

NCMP_DMI_HTTPCLIENT_IDLECONNECTIONEVICTIONTHRESHOLDINSECONDS

The default value for this parameter was 5 seconds and we increased it 30 seconds.

There is one timeout variable defined in the DmiDataOperations class

• private static final long DEFAULT_ASYNC_TASK_EXECUTOR_TIMEOUT_IN_MILLISECONDS = 30000L;

We would like to increase this value to see if that would fix this issue.

EDIT: We have built an NCMP image with the aforementioned CPS changes but the issue still persist

Adding the NCMP logs to the ticket.

Thank you!