Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via GitHub by ShekharWNC
, 2 years ago
Parser got END_DOCUMENT event. This could happen e.g. if the server closed the connection without sending a closing stream element
via igniterealtime.org by Unknown author, 1 year ago
Parser got END_DOCUMENT event. This could happen e.g. if the server closed the connection without sending a closing stream element
via Stack Overflow by arslan haktic
, 1 year ago
Parser got END_DOCUMENT event. This could happen e.g. if the server closed the connection without sending a closing stream element
via Stack Overflow by Unknown author, 2 years ago
Parser got END_DOCUMENT event. This could happen e.g. if the server closed the connection without sending a closing stream element
via Stack Overflow by anupam x
, 2 years ago
Parser got END_DOCUMENT event. This could happen e.g. if the server closed the connection without sending a closing stream element
via Stack Overflow by Aris
, 1 year ago
Parser got END_DOCUMENT event. This could happen e.g. if the server closed the connection without sending a closing stream element
org.jivesoftware.smack.SmackException: Parser got END_DOCUMENT event. This could happen e.g. if the server closed the connection without sending a closing stream element	at org.jivesoftware.smack.tcp.XMPPTCPConnection$PacketReader.parsePackets(XMPPTCPConnection.java:1170)	at org.jivesoftware.smack.tcp.XMPPTCPConnection$PacketReader.access$300(XMPPTCPConnection.java:952)	at org.jivesoftware.smack.tcp.XMPPTCPConnection$PacketReader$1.run(XMPPTCPConnection.java:967)	at java.lang.Thread.run(Thread.java:745)