What version of Spark do you use. Can you try with 2.6.0 Beta 2? What is the file extension (doc, zip, etc)? What is the size of the file? What server do you use and are there any download related settings changed?
I tried with the 2.6.0 Beta 2 version of Spark and am getting the same as well. The Spark clients and Openfire server (3.60a) are all running on the same
linux box. The clients are able to have a regular chat session fine.
The Spark client and server are on the same machine, so there are no firewall issues. (I can telnet to the 7777 port on the same machine with no issue)
Thanks for the suggestions - although, unfortunately I still get the same behavior when trying clients on different machines (I can telnet from one machine to the other on the port 7777)
Note well that the request to begin the stream is sent to the full JID
(user@host/resource) of the XMPP entity identified by the XMPP IRI/URI.
Therefore, the IRI/URI SHOULD include a full JID. If it does not, the
receiver MUST discover a full JID via presence or service discovery. If
the receiver cannot discover a full JID for the sender (e.g., in the
last resort through sending a presence subscription request to the
sender and receiving presence from the sender’s resources), then it
SHOULD abort the file transfer exchange.
Try sending the file to the full JID (username@servername/resource). As i understand the specs, if you can’t find out receiver’s full JID you should be subscribed to his presence.
Also you can try this with some other clients (on both sides), without adding a contact to a roster. You will have to unsubscribe first. So, maybe not only Spark is behaving like that.