Expert Advice

JVM_Lock_Missed_Critical  
Situation Description
Suggested Actions
Situation Description

Critical threshold exceeded for Lock Missed

 

Possible Causes
  1. Application code requested a lock on an object or a section of code, but the lock was already held by another thread.

 

Suggested Actions

The named lock object has a high proportion of misses. This means the lock must be retried and results in a delay to the application. Use the Lock Analysis workspace to determine if multiple threads wait for the same lock. Based on this, the application code should be reviewed to see whether synchronized blocks of code are used unnecessarily or inappropriately.

 

Copyright IBM Corp. 2016 All Rights Reserved US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contact IBM