-
Notifications
You must be signed in to change notification settings - Fork 371
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
A lot of errors. #74
Comments
The socket hung up (connection terminated). We may need to catch that from the SSL layer. |
I'm using prosody... Erro in prosody is: invalid-namespace, closing session. |
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? |
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. |
I looked at prosody source, when it call 'cb_error(session, "no-stream");' is where invalid-namespace happen
|
Is what I said possible? Use node-xmpp between socket.io and a xmpp server? to controll more then 300 connections? |
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? |
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. |
Im receiving a lot of errors... any ideia?:
events.js:48
throw arguments[1]; // Unhandled 'error' event
^
Error: socket hang up
at SecurePair.error (tls.js:802:15)
at CleartextStream._done (tls.js:283:17)
at CleartextStream._pull (tls.js:426:12)
at SecurePair.cycle (tls.js:727:20)
at CleartextStream.end (tls.js:256:13)
at Client.onEnd (/root/awesome-im/node_modules/node-xmpp/lib/xmpp/connection.js:279:17)
at Socket. (/root/awesome-im/node_modules/node-xmpp/lib/xmpp/connection.js:56:14)
at Socket.emit (events.js:88:20)
at TCP.onread (net.js:388:51)
The text was updated successfully, but these errors were encountered: