The Health Center shows:
“java/lang/ClassLoader$CacheTable@0000000082560030 (Object)" had a high miss percentage indicating that 38% of attempts by a thread to own the lock (when the requesting thread did not already own it) required the thread to wait. Reducing contention on this lock could result in a performance improvement.”
Unfortunately Heatlh Center does not show us the calling methods' stacks. Hence we are not able to identify which application package/class is causing this issue. We are not able to resolve this issue at this point.
Does anybody have any suggestion on how to know which classes/methods are using this lock? With or without Health Center?
Thanks for any help.
NOTICE: developerWorks Community will be offline May 29-30, 2015 while we upgrade to the latest version of IBM Connections. For more information, read our upgrade FAQ.
This topic has been locked.