powered by Jive Software

Openfire 3.3.0: Stream issue

During the transfer of large XMPP packages, exceeding 20000 symbols to an External component, zero symbols appear on the TCP packages’ joints, what leads to errors in the functioning of XML parser.

Is this a known problem?

for instance:

ctime=“20070324T184132” /><report u???uid=“b411dba0-6c79-4459-8c59-9178bdf91928”

instead of:

ctime=“20070324T184132” /><report uuid=“b411dba0-6c79-4459-8c59-9178bdf91928”

Message was edited by: Alexander Golubev

Does nobody know?

Hey Alexander,

Is there a way for you to send me a piece of code that reproduces that problem? I would like to analyze it while the problem is happening in my local machine. I have no ideas so far.


– Gato

Hi, dombiak_gaston.

I can not send you a part of code, because it is highly coupled. But any large XMPP packages can reproduce this issue, for instance:

+<iq to=“server” type=“set” id=“123” from=“demo@server/client”>

<message arg=“0”/>

<message arg=“1”/>

<message arg=“1022”/>

<message arg=“1023”/>


as a result:

+org.jivesoftware.wildfire.nio.ConnectionHandler.messageReceived(ConnectionHandle r.java:133) Closing connection due to error while processing message: …

org.xmlpull.v1.XmlPullParserException: expected = after attribute name (position: END_TAG seen … @1:1433)

at org.xmlpull.mxp1.MXParser.parseAttribute(MXParser.java:2004)

at org.xmlpull.mxp1.MXParser.parseStartTag(MXParser.java:1799)

at org.jivesoftware.wildfire.net.MXParser.nextImpl(MXParser.java:190)+

if Wildfire|Openfire or:

+javax.xml.stream.XMLStreamException: ParseError at :[1,8502]

Message: Character reference “&#0” is an invalid XML character.

at com.sun.xml.stream.XMLReaderImpl.next(XMLReaderImpl.java:508)

at com.sun.xml.stream.XMLReaderImpl.getElementText(XMLReaderImpl.java:748)+

in External component.





Does anybody know?

up with a link to http://www.igniterealtime.org/forum/thread.jspa?threadID=26436 which may be related

Thank you.

JM-1062 to track it - I guess that no voting is required to get it resolved soon.