tools4j / mmap / 41181390251

push

github

Stop async map-ahead at the file mapper's mapping limit

Mapping ahead beyond the max file size of a non-rolling file threw on the
async mapper thread, which left the map-ahead slot owned by the mapper: it
retried the same failing request in a busy loop, logging the error each time,
and the slot was lost to the requester.

FileMapper now reports its mappingLimit (max file size, or Long.MAX_VALUE for
rolling and read-only mappers), and AsyncRunAheadRegionMapper does not map
ahead beyond it. A failing map-ahead is treated like a NULL_ADDRESS result so
the slot is always handed back; the requester maps synchronously when needed.

1669 of 1913 branches covered (87.25%)

Branch coverage included in aggregate %.

11 of 11 new or added lines in 6 files covered. (100.0%)

4547 of 4848 relevant lines covered (93.79%)

4.02 hits per line