Explicit odd int (s) visible after build

Question

I have a java class with a non-finite int variable that I explicitly initialized in the constructor to 0. All other variable calls are controlled by ReentrantLock. Should I worry that the threads will not see the initial value of 0, because I did not use the lock in the constructor?

Answer 1

Yes, you have to worry. To avoid problems in this case, you need to securely publish an object reference.

From Java Concurrency in practice :

, , . :

• ;
• volatile AtomicReference;
• ;
• , .

() , new (- ).

, , 0 , , , (JLS §17.4.4):

• (, ) - . , ,

Answer 2

Java Concurrency :

, , , .

, . "-". , , Concurrency. . .

, :

, . :

;

volatile field AtomicReference;

;

. , " ".

, , , (, , LinkedBlockingQueue ..).

, int ( 64- , long) , , "" , - - . , ( , , , , , ).

, , 0, .