Has anybody induced such a stack trace before?

What I think could be a potential contributor to the behaviour is that
https appears to have its own agent socket limit, separate from http. We
had a similar problem last year with http (although symptoms were
different) that was resolve by applying a greater number of maxSockets. By
additionally adjusting for https, we have not encountered the problem so
far.

http.globalAgent.maxSockets = 20000;
https.globalAgent.maxSockets = 20000;


thanks,
Aaron


On Thu, Jul 18, 2013 at 11:00 PM, Aaron Seet <[email protected]> wrote:


> The interesting thing was, after telling my colleague to revert back to
> plain http to communicate with the websocket server, while he could
> establish the socket connection, he would get reported errors from the
> socket layer because itself couldn't communicate with the backend. Looking
> at our websocket application log there were indeed trouble for our server
> acting as a client to the backend. So not only is client-to-websocket SSL
> failing, websocket-to-backend SSL is also failing.
>
> 2013-07-11 01:36:19.497 ERROR socket - [Error: 1744:error:14094418:SSL
> routines:SSL3_READ_BYTES:tlsv1 alert unknown
> ca:openssl\ssl\s3_pkt.c:1234:SSL alert number 48
> ]
> Error: 1744:error:14094418:SSL routines:SSL3_READ_BYTES:tlsv1 alert
> unknown ca:openssl\ssl\s3_pkt.c:1234:SSL alert number 48
> at CleartextStream._pusher (tls.js:656:24)
> at SlabBuffer.use (tls.js:199:18)
> at CleartextStream.CryptoStream._push (tls.js:483:33)
> at SecurePair.cycle (tls.js:880:20)
> at EncryptedStream.CryptoStream.write (tls.js:267:13)
> at Socket.ondata (stream.js:38:26)
> at Socket.EventEmitter.emit (events.js:96:17)
> at TCP.onread (net.js:397:14)
>
>
> And there were well over thirty port 443 TCP sockets pending to the backend
>
> TCP websocket_ip:56168 backend_ip:443 FIN_WAIT_2
>
> Don't have enough experience with the networking protocols to piece
> together a picture that hints at the problem, and a solution. Anybody seen
> similar situations before?
>
>
> thanks,
> Aaron
>

-- 
-- 
Job Board: http://jobs.nodejs.org/
Posting guidelines: 
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

--- 
You received this message because you are subscribed to the Google Groups 
"nodejs" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to