Why does assigning a nullable Integer to int throw before the next statement?

The assignment can contain an implicit method call even though the source shows no dot operator. A primitive cannot represent a missing quantity. For an optional stock count, keep Integer until the boundary where absence has a defined meaning. If missing really means zero, write int count = boxed == null ? 0 : boxed.intValue();. Otherwise reject the missing field with a clear validation error; replacing it with zero would silently change the data. Inspect the first application stack frame, not the later println. Verify null, zero and a positive count separately. Also inspect comparisons and mixed primitive/boxed ternary expressions, which can introduce another unboxing step. This correction does not make concurrent replacement of a shared object safe; capture the value once first.