JAVA.CONCURRENCY.UG.PARAM : Unguarded Parameter (Java)

Summary

A parameter of a method or constructor is accessed without the expected lock being held.

Java uses synchronized statements and methods to guarantee that data is accessed in a sequential way and avoid race conditions in multithreaded applications. Incorrect uses of synchronization result in unexpected behaviors and subtle bugs, very hard to identify and reproduce.

Checks for this warning class make use of annotations @com.juliasoft.julia.checkers.guardedBy.GuardedBy and @com.juliasoft.julia.checkers.guardedBy.Holding. Add these annotations to your code to identify synchronization requirements for CodeSonar to check.

The @GuardedBy annotation for fields and parameters and the @Holding annotation for methods and constructors accept a string argument, according to the following syntax.

• @GuardedBy/@Holding("this"): the lock on the receiver of a non-static field or method must be held
• @GuardedBy("itself"): the lock on the same parameter or field must be held
• @GuardedBy/@Holding("field-name"): the lock on the named field of the receiver of a non-static field or method must be held
• @GuardedBy/@Holding("Class.field-name"): the lock on the named static field of the named class must be held
• @GuardedBy/@Holding("Class.class"): the lock of the unique class object representing the class named Class must be held
• @GuardedBy/@Holding("foo()"): the lock on the return value of the named instance method called on the receiver of a non-static field or method must be held. Method foo must return a reference type
• @GuardedBy/@Holding("Class.foo()"): the lock on the return value of the named static method of the named class must be held. Method foo must return a reference type.

Properties

WARNING_FILTER += allow class="Unguarded Parameter (Java)"

Resolution

Verify if the missing synchronization should actually be there. Annotate fields and methods with the lock that must be held when they are accessed or called, by using the @GuardedBy and @Holding annotations. If this checker does not accept those annotations, it is likely the case that your program has a synchronization problem.

Relevant Configuration File Parameters

The following configuration file parameters affect checks for this warning class.

• JAVA_ANALYSIS_CONCURRENCY_CALLS
• JAVA_ANALYSIS_CONCURRENCY_GUARDS_MODE
• JAVA_ANALYSIS_DEEP_NULLNESS_CONSERVATIVE_CHECK
• JAVA_ANALYSIS_FAST_DEEP_CHECK
• JAVA_ANALYSIS_FIELD_SENSITIVE
• JAVA_ANALYSIS_INITIALIZATION_CHECK
• JAVA_ANALYSIS_MERGE_CREATION_POINTS
• REPORT_SIMILAR_WARNINGS
• WARNING_FILTER