```
new SimpleDateFormatDateService().iso8601DateParse("2013-08-08T20:52:29+0000");
java.lang.IllegalArgumentException: Error parsing data at 19
at
org.jclouds.date.internal.SimpleDateFormatDateService.iso8601DateParse(SimpleDateFormatDateService.java:149)
at Dummy.main(Dummy.java:37)
Caused by: java.text.ParseException: Unparseable date:
"2013-08-08T20:52:29+0000"
```
does indeed fail, but
```
new
SimpleDateFormatDateService().iso8601SecondsDateParse("2013-08-08T20:52:29+0000");
Thu Aug 08 16:52:29 EDT 2013
```
which is also provided by jclouds, succeeds.
Since there is currently an explicit distinction in the code between the two
formats, my initial interpretation would be that we are calling the wrong
parsing method.
That's assuming this problem occurs for a specific AWS call and not
intermittently across multiple calls, in which case the strict parsing
assumption (with vs. without millis) would probably have to be relaxed.
Could you provide a reproducible test case for this? Please then [open an
issue](https://issues.apache.org/jira/browse/JCLOUDS) for this problem.
Thanks!
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/105#issuecomment-22456847
