 
                            ...
Using an instance lock to protect static shared data can result in nondeterministic behavior.
| Rule | Severity | Likelihood | 
|---|
| Detectable | Repairable | Priority | Level | 
|---|---|---|---|
| LCK06-J | Medium | Probable | Yes | 
| No | P8 | L2 | 
Automated Detection
Some static analysis tools can detect violations of this rule.
| Tool | Version | Checker | Description | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Parasoft Jtest | 
 | CERT.LCK06.INSTLOCK | Do not use an instance lock to protect shared static data | ||||||
| SpotBugs | 
 | SSD_DO_NOT_USE_INSTANCE_LOCK_ON_SHARED_STATIC_DATA | Implemented since 4.6.0 | 
Related Guidelines
Bibliography
| [API 2014] | 
Issue Tracking
| Tasklist | ||||
|---|---|---|---|---|
| 
 | ||||
| ||Completed||Priority||Locked||CreatedDate||CompletedDate||Assignee||Name|| |T|M|F|1270215165305|1271447005294|rcs_mgr|"Ideally, the lock should also be private and final" => I have been penalized for using "ideally" before. I would just remove that sentence or make it more definitive. Note that we also have an NCE that uses method synchronization. Perhaps we also need a CS with a static method.| | 
...
...