A lot of errors. about xmpp.js HOT 8 CLOSED

The socket hung up (connection terminated). We may need to catch that from the SSL layer.

from xmpp.js.

I'm using prosody... Erro in prosody is: invalid-namespace, closing session.

from xmpp.js.

Now that is interesting. Would you please determine which xmlns declaration is the culprit? Are you perhaps trying to connect a Component to a c2s port or vice versa?

from xmpp.js.

So, I'm trying to make a webchat. Normally, a webchat whould connect to prosody using a BOSH. But, I tried to make my webchat using socket.io, and node/socket.io uses node-xmpp to real connect to prosody... it not working ;)

Into development everthing works just fine... but in production, with more then 300 users online, this issue happen all the time (and node server restart).

At production, node-xmpp reconnect all the time as well. (when "reconnect: true" is setted)

I'll try to find more information about this issue.

from xmpp.js.

I looked at prosody source, when it call 'cb_error(session, "no-stream");' is where invalid-namespace happen

      if not stanza then --if we are not currently inside a stanza
        if session.notopen then
            if tagname == stream_tag then
                non_streamns_depth = 0;
                if cb_streamopened then
                    cb_streamopened(session, attr);
                end
            else
                -- Garbage before stream?
                cb_error(session, "no-stream");
            end
            return;
        end
        if curr_ns == "jabber:client" and name ~= "iq" and name ~= "presence" and name ~= "message" then
            cb_error(session, "invalid-top-level-element");
        end

        stanza = st.stanza(name, attr);
    else -- we are inside a stanza, so add a tag
        stanza:tag(name, attr);
    end

from xmpp.js.

Is what I said possible? Use node-xmpp between socket.io and a xmpp server? to controll more then 300 connections?

from xmpp.js.

Sure, that sounds like a proxy server to me. Take a look at node-xmpp-bosh for example, they do something quite similar.

Did you resolve that invalid-namespace error by now? Can we close this bug?

from xmpp.js.

Now, I dont using node-xmpp as a proxy anymore... but I'll try again. For now, we can close this issue. I re open it in future, if necessary.

from xmpp.js.