Unparseable date

Smack Smack Dev
21

Daniel can explain that better. Probably it’s a bug both in Openfire and Smack.

22

I have just created a ticket for it SMACK-243, so it won’t be missed.

23

wroot wrote:

Anyway, please test that with next version of Openfire and then report back.

I have tested this with 3.5.2 version of Openfire and it wasnt fixed, so Daniels fixes were about something else.

24

Hello ,

is Anybody working this critical bug or any plans for fixing , we facing lots of issues due to this bug already faced downtimes.Looks smack is not able handle certain kinds of well-formed, but otherwise defective XML packets http://www.igniterealtime.org/issues/browse/SMACK-232 to which this bug is related http://www.igniterealtime.org/issues/browse/SMACK-243 . it also look this maybe exeption maybe caused by java date parsing bug http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=5087246

I request some one for Jive /Sr member of community to have a look at this and release a emergency patch

if there no plans to fix soon then please let us know , we will migrate to other libraries like echomine and/or in meantime try to fix it ourselfs which might take some time

25

As assignee of SMACK-243 has just changed, i suppose there should be some work done on this soon.

26

Hi!
I have the same (i think) problem, byt when i send file from beetwen JBother and my program.
What is strange, that JBrother also is using smack ( I heard).

java.text.ParseException: Unparseable date: "2008-12-17T09:51:09Z"
at java.text.DateFormat.parse(Unknown Source)
at org.jivesoftware.smackx.provider.StreamInitiationProvider.parseIQ(StreamInitiat ionProvider.java:96)
at org.jivesoftware.smack.PacketReader.parseIQ(PacketReader.java:597)
at org.jivesoftware.smack.PacketReader.parsePackets(PacketReader.java:275)
at org.jivesoftware.smack.PacketReader.access$000(PacketReader.java:44)
at org.jivesoftware.smack.PacketReader$1.run(PacketReader.java:76)

I know that this bug was noticed (SMACK-243) but I just want to mention that my date format is a little bit different than that in bug

27

I’m getting the original problem

Unparseable date: “200911T2:48:11”

ever since the new year for one of our users but just for one… I dont get why is google sending proper data for all others, including me that are in new year already. Can it be actually client problem on the other side sending nonsense? After I added override check it was just one that got into that place…

Anyway, I hacked source of DelayInformationProvider directly because we already had 2 hrs downtime due to this. Not sure whats the proper way to solve the problem… cause if the format goes like this how would you know

2009111 as jan/11 or nov/1st? I guess I need to find the real docs about what google can send… any clues/links/info?

One way or the other, the fact that packet error is killing the client is just atocious… I guess I’ll have to change it myself again…

28

Proper ticket link http://www.igniterealtime.org/issues/browse/SMACK-243

Strange, but this critical issue is not getting an attention.

29

Hi

I had same problems. Working on it I found and fixed an error on:

src\java\org\jivesoftware\util\XMPPDateTimeFormat.java

changing:

ln 99: Matcher xep82WoMillisMatcher = xep80DateTimePattern.matcher(dateString);
ln 100: Matcher xep82Matcher = xep80DateTimeWoMillisPattern.matcher(dateString);

for

ln 99: Matcher xep82Matcher = xep80DateTimePattern.matcher(dateString);
ln100: Matcher xep82WoMillisMatcher = xep80DateTimeWoMillisPattern.matcher(dateString);

Best Regards

Marcelo

30

This issue is tracked as OF-646 and the fix will be included in the next release.