[nodejs] Fix issue with connection failures silently failing#1480
[nodejs] Fix issue with connection failures silently failing#1480dorilla wants to merge 1 commit intoapache:0.9.3from
Conversation
jeking3
left a comment
There was a problem hiding this comment.
This needs to be retargeted at the master branch.
jeking3
left a comment
There was a problem hiding this comment.
This needs to be retargeted at the master branch and it needs an Apache Jira thrift ticket. See https://thrift.apache.org/docs/HowToContribute
|
This needs to be retargeted at the master branch and it needs an Apache Jira thrift ticket. See https://thrift.apache.org/docs/HowToContribute |
|
@bananer apart from missing any testing, is this a reasonable enhancement? |
|
@jeking3 This looks reasonable. Should have tests, though. |
|
Apologies, I haven't had the time to update this ticket. I fully intend to, just trying to find the time. |
|
Just a reminder, if you can move this forward based on the conversation above please do. Thanks. |
|
This is targeting the wrong branch. Closing. |
In node, when a connection fails, the caller is not signaled the error, it simply hangs. This solution sends a generic
TApplicationExceptionwith details on the unreachable service.a connection failure is either:
To replicate:
ECONNREFUSEDerror occursAnother way to replicate:
setTimeout(callback, 10000);to simulate the long-running piece of workECONNRESETerror occursWith the proposed fix, the callback receives the proper error, as well as the promise option.