java.time.DateTimeException

Invalid value for NanoOfSecond (valid values 0 - 999999999): -842099582 ...


Solutions on the web14

Solution icon of github
via GitHub by sixcorners
, 7 months ago
Invalid value for NanoOfSecond (valid values 0 - 999999999): -842099582 ...

Solution icon of github
Invalid value for Year (valid values -999999999 - 999999999): -768614335404564651

Solution icon of stackoverflow
Invalid value for Year (valid values -999999999 - 999999999): 4090323145

Solution icon of stackoverflow
Invalid value for Year (valid values -999999999 - 999999999): -1000000001

Solution icon of stackoverflow
via Stack Overflow by EPMS Devteam
, 1 year ago
Invalid value for Era (valid values 0 - 1): 2

Solution icon of github
Invalid value for DayOfMonth (valid values 1 - 28/31): -1

Solution icon of stackoverflow
via Stack Overflow by Unknown author, 1 year ago
Unable to obtain LocalTime from TemporalAccessor: {MinuteOfHour=21, MilliOfSecond=0, NanoOfSecond=0, HourOfAmPm=0, MicroOfSecond=0, SecondOfMinute=24},ISO,Europe/Paris resolved to 2015-05-25 of type java.time.format.Parsed

Solution icon of stackoverflow
Unable to obtain Instant from TemporalAccessor: {InstantSeconds=1477571499, NanoOfSecond=84700000},ISO of type java.time.format.Parsed

Solution icon of stackoverflow
Invalid ID for ZoneOffset, non numeric characters found: Asia/Aden

Solution icon of stackoverflow
via Stack Overflow by adelmo00
, 5 months ago
Invalid ID for ZoneOffset, non numeric characters found: -3:00

Stack trace

  • java.time.DateTimeException: Invalid value for NanoOfSecond (valid values 0 - 999999999): -842099582 ... at java.time.Instant.toString(Instant.java:1330) at com.openpojo.log.utils.MessageFormatter.format(MessageFormatter.java:131)

Write tip

You have a different solution? A short tip here would help you and many other users who saw this issue last week.

Users with the same issue

You are the first who have seen this exception. Write a tip to help other users and build your expert profile.