java.lang.Thread.State: BLOCKED (on object monitor) in wrapper.log file during the discovery
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-17-2024 11:19 PM
when im executing a discovery schedular , I could see sometimes randomly out of 20 switches some 1/2/3 switches getting stuck at shazzam only which are not moving forward for the further probes and sensors. I tried restarting the mid servers and rediscover them again and still i could see the same pattern of switches getting stuck. I added the max.threads parameter, increased the snmp timedout as well in the midserver still the issue persists. later i found something like blocked (on object monitor) log in wrapper.log ...can anyone help me on this issue. its coming only with some midserver but not all.
- Labels:
-
Discovery
-
Orchestration (ITOM)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-18-2024 01:35 AM
Hi @HareeshPVR ,
Hard to crack such java.lang errors. recommend you to submit a support case with servicenow with agent and wrapper logs.. I hope my answer helps...
☑️ Please mark responses as HELPFUL or ACCEPT SOLUTION to assist future users in finding the right solution....