There are methods in some classes, which contain an unsynchronized lazy initialization of a non-volatile static field. Because the compiler or processor may reorder instructions, threads are not guaranteed to see a completely initialized object, if the method can be called by multiple threads. You can make the field volatile to correct the problem. For more information, see the Java Memory Model web site.
ModuleFactory (lines 451, 465, 509, etc), ServiceContext, DatabaseUpdater
Eliminate all such errors reported by sonar: