[jdev] Jabber and Flash: (seemingly) unprovoked stream errors

Kirschner, Larry Larry.Kirschner at mtvi.com
Thu May 20 12:45:46 CDT 2004

Thanks for responding. Servers are jabber1.4.3 and muc0.6. I think the
problem was related to JID resource identifiers and my fault (big
surprise). I was testing in the flash ide with a default login
hard-coded in and--since other developers are also working on the
client--I think we were ending up with multiple users with the same
jabber username and resource. I put in code to make the resources unique
and the problem seems to have gone away. 

-----Original Message-----
From: Sean Voisen [mailto:listsubscriber at voisen.org] 
Sent: Thursday, May 20, 2004 12:17 PM
To: Jabber software development list
Subject: Re: [jdev] Jabber and Flash: (seemingly) unprovoked stream

On Mon, 17 May 2004, Kirschner, Larry wrote:

> Sometimes this all works well. Other times, flash successfully 
> connects to jabber, joins the room, even gets a few events from the 
> room, but then out of nowhere gets a 
> <stream:error>Disconnected</stream:error> and jabber closes the 
> connection. Once it gets into this state, the scenario seems to repeat

> over and over. I've run TCP dump to see if I'm inadvertently sending
anything to jabber from flash, and I'm not.

Hi Larry,

There are definitely issues with Flash's XMLSocket, but I don't think
I've ever run into this behavior before. You said that after joining,
your client doesn't send any further messages to the MUC room ... I'm
wondering if it's related, but I don't think MUC needs messages in order
to keep the connection alive :)

I've had issues with the MUC component dying on me after long periods of
inactivity, but nothing as you describe. What server are you running?

- Sean

Sean Voisen
Weblog: http://voisen.org
Flash/XMPP: http://xifflabs.com
XIFF 2.0: http://www.jabberstudio.org/projects/xiff
jdev mailing list
jdev at jabber.org

More information about the JDev mailing list