@Marcelo Maybe you should mention that you where making these changes in the openfire source code. This is tracked as and has been fixed in the trunk.

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

fixed in revision 11823

moved the XEP_0082_UTC_FORMAT DateFormat from the core class Packet to the StringUtils class (as suggested by Guus).
Added synchronized methods to access the formatter and replaced all usage of the formatter with this methods.

Your stream error problem and the fixes of my patch are not connected.
The patch fixes parsing a <message> or <presence> tag containing a <delay> tag with an errornous date.

Your problem seems to be that one of the entities you are communicating with sends an error in the XML stream.
(<stream> ... <message>...</message> ... <error>text</error> ... </stream>). So you should check why this error is sent.