Why can an Object member variable not be both final and volatile in Java?

Question

If in a class I have a ConcurrentHashMap instance that will be modified and read by multiple threads I might define like this:

public class My Class {

    p         


        

Answer 1

A volatile field gives you guarantees as what happens when you change it. (No an object which it might be a reference to)

A final field cannot be changed (What the fields reference can be changed)

It makes no sense to have both.