This content has been marked as final. Show 3 replies
28 seconds sounds very near to 30s, the default Socket connection timeout on Linux....1 person found this helpful
If you are using JRockit, in JRMC there is an outstanding Latency analyzer, which lets you pick up even the tiniest wait time in every thread.
However, since 28 seconds is quite a human time, I would simply take thread dumps at 5 seconds interval (google for weblogic thread dump) and see where the thread(s) are blocking... most likely on a network i/o operation
Thanks. My research has also pointed to JRockit. I'll give this a try. I'm also looking at OS thread management. It also seems as though the Java thread gets swapped out.
Turns out the issue was related to OS level SNMP port IO timeout. There were routing issues causing DNS lookups a long time to resolve. This in-turn caused delays up to 28+ seconds in the JDMK SNMP manager during some snmpGet of OIDs and MIB tables. Since the same JDMK SNMP manager is used from trap recipient and listener it also caused delays in processing traps. We solved the issue by updating the resolv.conf to something that worked. This was verified using nslookup and traceroute commands on Linux.