Notice I said process.on('error') and process.on('exit') NOT
connection.on(*). If this is something that is happening lower than the
socket level you may not be able to catch it at the socket level. Since
your getting an ECONREFUSED error after the socket is stableized (sp?) and
running I'd see if I couldn't catch the app error instead.
BTW: Are you using any IPC stuff in your code, if so you may be chasing the
wrong crash? I've had that same error come from Hook's (unrelated I'm
sure) when trying to use fork instead of spawn.
- Jeremy
On Wed, Feb 22, 2012 at 1:24 PM, Demián Andrés Rodriguez <[email protected]
> wrote:
> But the thing is that now the connection ends without emitting any 'error'
> or 'end' event. I've registered a listener for every damn event the request
> & response emits, what am I missing?
>
> We are not behind a firewall:
>
> root@w5:/var/www/nsnode# lscpu
> Architecture: x86_64
> CPU op-mode(s): 32-bit, 64-bit
> CPU(s): 16
> Thread(s) per core: 2
> Core(s) per socket: 4
> CPU socket(s): 2
> NUMA node(s): 2
> Vendor ID: GenuineIntel
> CPU family: 6
> Model: 44
> Stepping: 2
> CPU MHz: 2399.956
> Virtualization: VT-x
> L1d cache: 32K
> L1i cache: 32K
> L2 cache: 256K
> L3 cache: 12288K
>
>
> On Wed, Feb 22, 2012 at 4:16 PM, Jeremy Darling
> <[email protected]>wrote:
>
>> OS, Num CPUs, Firewall or no Firewall, etc etc please. Lots of things
>> can cause a connection to be terminated that are in and out of scope for
>> any application.
>>
>> As for catching you can use process.on('error') or process.on('exit') or
>> try{}catch(e){} and retry logic depending on where the line is getting cut.
>>
>> - Jeremy
>>
>>
>> On Wed, Feb 22, 2012 at 10:01 AM, Rambo <[email protected]> wrote:
>>
>>> I'm also experiencing random disconnects without any emitted errors,
>>> that's just bizarre. I'm sure the server is not causing the disconnection.
>>> What could be happening?
>>>
>>> --
>>> 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
>>>
>>
>> --
>> 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
>>
>
> --
> 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
>
--
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
