Inconsistent synchronization of getter/setter attribut - sonar critical issue
<p>I couldn't fix the following Sonar critical issue:</p>

<blockquote>
  <p>Inconsistent synchronization of address; locked 60% of time</p>
</blockquote>

<p>adress is a private attribut in a java class with its getter and its setter as follows:</p>

<pre><code>private String address;
public String getAddress() {
        return this.address;
}
public void setAddress(String address) {
        this.address = address;
}
</code></pre>

<p>have an idea how to fix it? or how can i know that address is Inconsistent synchronization ?</p>

<p>The rule of the issue given by sonar is :</p>

<blockquote>
  <p>The fields of this class appear to be accessed inconsistently with
  respect to synchronization.  This bug report indicates that the bug
  pattern detector judged that</p>
  
  <p>The class contains a mix of locked and unlocked accesses, At least one
  locked access was performed by one of the class's own methods, and The
  number of unsynchronized field accesses (reads and writes) was no more
  than one third of all accesses, with writes being weighed twice as
  high as reads A typical bug matching this bug pattern is forgetting to
  synchronize one of the methods in a class that is intended to be
  thread-safe.</p>
  
  <p>You can select the nodes labeled "Unsynchronized access" to show the
  code locations where the detector believed that a field was accessed
  without synchronization.</p>
  
  <p>Note that there are various sources of inaccuracy in this detector;
  for example, the detector cannot statically detect all situations in
  which a lock is held.  Also, even when the detector is accurate in
  distinguishing locked vs. unlocked accesses, the code in question may
  still be correct.</p>
</blockquote>