Lack of checked integer arithmetic in some form is what I think is Java's biggest failure. Next to it is a lack of unsigned less/greater-than operator; it cannot be emulated easily with signed arithmetic. [There is unsigned right shift.]
(.Net _does_ have checked arithmetic; at least as an option.)
Pure JavaScript code isn't vulnerable to integer overflow by virtue of not having any integer types, and I believe errors like this were the reason for leaving them out of the language.
In fact, if incremented repeatedly, 64-bit floats lose precision before 64-bit ints overflow.
More precisely, a 64 bit IEEE 754 ("double precision") has 53 bits worth of "integer"[0], which allows for 15 digits (and almost, but not quite, 16: it can encode 15.95 decimal digits)
[0] even though only 52 bits are allocated to the fraction, because the fraction part has an implicit 53rd bit set to 1 outside of special values
[1] https://en.wikipedia.org/wiki/Arbitrary-precision_arithmetic
In languages where integer overflow is possible, my point still holds.