Hello Frank,
The issue got reproduced after some more trials. I have enabled the agent pp logging.
It shows the below warning,
19700101.00:30:55: -1388104624: (9)DEBUG : Synchronized: try lock busy (id)(ptr): (354), (21119904)
Please find the last few portions of the logs below.
19700101.00:30:51: -1431309232: (7)DEBUG : Vacm: Access requested for: (viewName) (oid): (defaultViewNtcip), (1.3.6.1.4.1.1206.4.2.7.4.1.0)
19700101.00:30:51: -1431309232: (7)DEBUG : Vacm: isInMibView: (viewName) (subtree): (defaultViewNtcip), (1.3.6.1.4.1.1206.4.2.7.4.1.0)
19700101.00:30:51: -1431309232: (8)DEBUG : VacmViewTreeFamilyTable: isInMibView: (viewName) (match): (defaultViewNtcip), (v1ReadView)
19700101.00:30:51: -1431309232: (8)DEBUG : VacmViewTreeFamilyTable: isInMibView: (viewName) (match): (defaultViewNtcip), (v1WriteView)
19700101.00:30:51: -1431309232: (8)DEBUG : VacmViewTreeFamilyTable: isInMibView: (viewName) (match): (defaultViewNtcip), (v1NotifyView)
19700101.00:30:51: -1431309232: (8)DEBUG : VacmViewTreeFamilyTable: isInMibView: (viewName) (match): (defaultViewNtcip), (newView)
19700101.00:30:51: -1431309232: (8)DEBUG : VacmViewTreeFamilyTable: isInMibView: (viewName) (match): (defaultViewNtcip), (testView)
19700101.00:30:51: -1431309232: (8)DEBUG : VacmViewTreeFamilyTable: isInMibView: (viewName) (match): (defaultViewNtcip), (internet)
19700101.00:30:51: -1431309232: (8)DEBUG : VacmViewTreeFamilyTable: isInMibView: (viewName) (match): (defaultViewNtcip), (restricted)
19700101.00:30:51: -1431309232: (8)DEBUG : VacmViewTreeFamilyTable: isInMibView: (viewName) (match): (defaultViewNtcip), (defaultViewNtcip)
19700101.00:30:51: -1431309232: (9)DEBUG : Vacm: isInMibView: access allowed
19700101.00:30:51: -1431309232: (9)DEBUG : Synchronized created (id)(ptr): (3290), (-1389344736)
19700101.00:30:51: -1431309232: (9)DEBUG : Synchronized created (id)(ptr): (3291), (-1431312296)
19700101.00:30:51: -1431309232: (2)DEBUG : LockQueue: adding lock request (ptr): (-1389344736)
19700101.00:30:51: -1383947184: (8)DEBUG : Synchronized: try lock success (id)(ptr): (3290), (-1389344736)
19700101.00:30:51: -1383947184: (8)DEBUG : LockQueue: lock (ptr)(pending): (-1389344736), (1)
19700101.00:30:51: -1383947184: (9)DEBUG : LockQueue: waiting for next event (pending): (0)
19700101.00:30:55: -1388104624: (9)DEBUG : Synchronized: try lock busy (id)(ptr): (354), (21119904)
19700101.00:30:55: -1388104624: (9)DEBUG : LockQueue: waiting for next event (pending): (1)
19700101.00:30:56: -1383947184: (9)DEBUG : LockQueue: waiting for next event (pending): (0)
19700101.00:31:00: -1388104624: (9)DEBUG : Synchronized: try lock busy (id)(ptr): (354), (21119904)
19700101.00:31:00: -1388104624: (9)DEBUG : LockQueue: waiting for next event (pending): (1)
19700101.00:31:01: -1383947184: (9)DEBUG : LockQueue: waiting for next event (pending): (0)
By any chance, the add_request API could wait in this scenario? Because I didn’t see any logs after that. I had put some extra logs in my application.
We are using AgentPP version 4.1.2, Is there any changes related to this scenario committed in the latest releases?
The issue here is if the thread pool size is 8 and you give more than 10 requests at a time, The thread never comes out of the add_request call.
Please let me know if you need any more information.