Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Cannot Reproduce
-
Affects Version/s: 1.3.1
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
-
JDK version and platform:1.5.0_07
Description
06 Mar 2012 15:13:48.668 [ERROR] [WorkerThread32] [xxx.xx.xx.xxxx.xxxxxxxx.xxxxxxxxxxxxxxxxxx] - Exception caught in xxxxxxxxxxxxxxxxxx:
com.thoughtworks.xstream.converters.ConversionException: Unable to parse the date value:2012-03-06 15:12:44. Expected to be in format yyyy-MM-dd HH:mm:ss : Unable to parse the date value:2012-03-06 15:12:44. Expected to be in format yyyy-MM-dd HH:mm:ss
---- Debugging information ----
message : Unable to parse the date value:2012-03-06 15:12:44. Expected to be in format yyyy-MM-dd HH:mm:ss
cause-exception : java.lang.IllegalStateException
cause-message : Unable to parse the date value:2012-03-06 15:12:44. Expected to be in format yyyy-MM-dd HH:mm:ss
Activity
You can ignore this for now.
Converstion Solutions
added a comment - You can ignore this for now. OK, please reopen, if you can provide more information.
Jörg Schaible
added a comment - OK, please reopen, if you can provide more information. Oh, and I can remember for such an error that can be be solved by upgrading JDK. _07 is really buggy.
Jörg Schaible
added a comment - Oh, and I can remember for such an error that can be be solved by upgrading JDK. _07 is really buggy. Thanks. It definitely seems like it's failing to parse due to the parser. I don't think it has anything to do with xstream.
Converstion Solutions
added a comment - Thanks. It definitely seems like it's failing to parse due to the parser. I don't think it has anything to do with xstream. 
Can you please try latest XStream version 1.4.2?