504 Gateway Timeout ELB
up vote
0
down vote
favorite
This is my current project set up.
Client --> AWS ELB (Classic) -->Node Js ---> AWS ELB (Classic) --> Tomcat (Java Application)
I have the AWS ELB's idle time out configured to 600 seconds across all the instances. Also nodeJS server timeouts are set to 600 seconds using server.setTimeout() .
When i execute a request from the browser after around two minutes i get a 504 Gateway Timeout error.
After researching online and following suggestions i was able to narrow down the problem to AWS ELB connecting to the Node JS. Also turning ELB logs did not yield any exceptions to pinpoint the problem .
My client code is react based and we use request (http) library to make the connections to node.js . No where in the client code we set the timeout in http calls.
Why does the ELB times out after 2 minutes in spite of having the idle timeout set at 600 seconds (10 minutes)?
Where else should i look for the 2 minute timeout setting in the above set up? Does the request library have any default timeout?
node.js amazon-web-services
asked Nov 10 at 3:40
user7246161
345
add a comment |
up vote
0
down vote
favorite
This is my current project set up.
Client --> AWS ELB (Classic) -->Node Js ---> AWS ELB (Classic) --> Tomcat (Java Application)
I have the AWS ELB's idle time out configured to 600 seconds across all the instances. Also nodeJS server timeouts are set to 600 seconds using server.setTimeout() .
When i execute a request from the browser after around two minutes i get a 504 Gateway Timeout error.
After researching online and following suggestions i was able to narrow down the problem to AWS ELB connecting to the Node JS. Also turning ELB logs did not yield any exceptions to pinpoint the problem .
My client code is react based and we use request (http) library to make the connections to node.js . No where in the client code we set the timeout in http calls.
Why does the ELB times out after 2 minutes in spite of having the idle timeout set at 600 seconds (10 minutes)?
Where else should i look for the 2 minute timeout setting in the above set up? Does the request library have any default timeout?
node.js amazon-web-services
asked Nov 10 at 3:40
user7246161
345
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
This is my current project set up.
Client --> AWS ELB (Classic) -->Node Js ---> AWS ELB (Classic) --> Tomcat (Java Application)
I have the AWS ELB's idle time out configured to 600 seconds across all the instances. Also nodeJS server timeouts are set to 600 seconds using server.setTimeout() .
When i execute a request from the browser after around two minutes i get a 504 Gateway Timeout error.
After researching online and following suggestions i was able to narrow down the problem to AWS ELB connecting to the Node JS. Also turning ELB logs did not yield any exceptions to pinpoint the problem .
My client code is react based and we use request (http) library to make the connections to node.js . No where in the client code we set the timeout in http calls.
Why does the ELB times out after 2 minutes in spite of having the idle timeout set at 600 seconds (10 minutes)?
Where else should i look for the 2 minute timeout setting in the above set up? Does the request library have any default timeout?
node.js amazon-web-services
asked Nov 10 at 3:40
user7246161
345
This is my current project set up.
Client --> AWS ELB (Classic) -->Node Js ---> AWS ELB (Classic) --> Tomcat (Java Application)
I have the AWS ELB's idle time out configured to 600 seconds across all the instances. Also nodeJS server timeouts are set to 600 seconds using server.setTimeout() .
When i execute a request from the browser after around two minutes i get a 504 Gateway Timeout error.
After researching online and following suggestions i was able to narrow down the problem to AWS ELB connecting to the Node JS. Also turning ELB logs did not yield any exceptions to pinpoint the problem .
My client code is react based and we use request (http) library to make the connections to node.js . No where in the client code we set the timeout in http calls.
Why does the ELB times out after 2 minutes in spite of having the idle timeout set at 600 seconds (10 minutes)?
Where else should i look for the 2 minute timeout setting in the above set up? Does the request library have any default timeout?
node.js amazon-web-services
node.js amazon-web-services
asked Nov 10 at 3:40
user7246161
345
asked Nov 10 at 3:40
user7246161
345
edited Nov 10 at 4:17
asked Nov 10 at 3:40
user7246161
345
asked Nov 10 at 3:40
user7246161
345
asked Nov 10 at 3:40
user7246161
345
345
add a comment |
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53235810%2f504-gateway-timeout-elb%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
