Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via GitHub by trr-amsiq
, 1 year ago
Cannot parse "2016-04-01": Illegal instant due to time zone offset transition (Asia/Amman)
via Atlassian JIRA by Janice Alor [Atlassian], 1 year ago
Cannot parse "2016-03-27": Illegal instant due to time zone offset transition (Asia/Beirut) 2016-04-18 17:49:02.777649500 at org.joda.time.format.DateTimeParserBucket.computeMillis(DateTimeParserBucket.java:471)
via Atlassian JIRA by Janice Alor [Atlassian], 2 years ago
Cannot parse "2016-03-27": Illegal instant due to time zone offset transition (Asia/Beirut) 2016-04-18 17:49:02.777649500 at org.joda.time.format.DateTimeParserBucket.computeMillis(DateTimeParserBucket.java:471)
via Stack Overflow by Unknown author, 2 years ago
Cannot parse "26.03 02:50": Illegal instant due to time zone offset transition (Europe/Moscow)
via Stack Overflow by Joshua
, 2 years ago
Cannot parse "2015-03-08 02:00:00.0": Illegal instant due to time zone offset transition (America/Chicago)
via GitHub by MisterY
, 2 years ago
Cannot parse "2016-03-13": Illegal instant due to time zone offset transition (America/Havana)
org.joda.time.IllegalInstantException: Cannot parse "2016-04-01": Illegal instant due to time zone offset transition (Asia/Amman) at org.joda.time.format.DateTimeParserBucket.computeMillis(SourceFile:471) at org.joda.time.format.DateTimeParserBucket.doParseMillis(SourceFile:182) at org.joda.time.format.DateTimeFormatter.parseMillis(SourceFile:826) at org.joda.time.convert.StringConverter.getInstantMillis(SourceFile:65) at org.joda.time.base.BaseDateTime.<init>(SourceFile:173) at org.joda.time.DateTime.<init>(SourceFile:257)