Start here

Home
About Klocwork
What's new
Fixed issues
Release notes
Installation

Reference

C/C++ checkers
Java checkers
C# checkers
MISRA C 2004 checkers
MISRA C++ 2008 checkers
MISRA C 2012 checkers
MISRA C 2012 checkers with Amendment 1
Commands
Metrics
Troubleshooting
Reference

Product components

C/C++ Integration build analysis
Java Integration build analysis
Desktop analysis
Refactoring
Klocwork Static Code Analysis
Klocwork Code Review
Structure101
Tuning
Custom checkers

Coding environments

Visual Studio
Eclipse for C/C++
Eclipse for Java
IntelliJ IDEA
Other

Administration

Project configuration
Build configuration
Administration
Analysis performance
Server performance
Security/permissions
Licensing
Klocwork Static Code Analysis Web API
Klocwork Code Review Web API

Community

View help online
Visit RogueWave.com
Klocwork Support
Rogue Wave Videos

Legal

Legal information

JD.SYNC.IN

JD.SYNC.IN is found when a class is using its own field inconsistently. "Inconsistently" means that the number of protected usages is greater than 66% of the number of all usages. The error is reported when the count of field usages is greater than three. These numbers are checker parameters that you can change.

Vulnerability and risk

Inconsistent synchronization can cause race conditions.

Mitigation and prevention

Fields should either be synchronized with the same lock all the time, or not synchronized at all. Partial synchronization is a root-cause of race condition problems.

Example 1

9      class MyClass {
10         private String name;
11         public MyClass() {
12             name = "";
13         }
14         synchronized public String getName() {
15             return name;
16         }
17         synchronized public void setName(String name) {
18             this.name = name;
19         }
20         public void foo(String x) {
21             name = x;
22         }
23     }

JD.SYNC.IN is reported for field declaration on line 10: Field 'name' synchronized inconsistently.