What are the possible reasons why a web API client request does not get to the API
I have two instances of an app running on IIS. Both apps asynchronously calls a web API hosted on a different server (running as a local service). At a point, requests from just one of the apps stops getting to the API. Just to be sure the API is still reachable from the server where the app is hosted, I initiated calls to the API via Postman, and everything goes fine.
Not too clear as to what the issue is exactly, but I can only think based on my level of understanding, that the app could not get further CPU(IO) resource to push further requests to the API.
While my next move is to use a packet sniffer to see if I can trace the requests on the server, I need help on what exactly has gone wrong, what am I to look out for and possible solutions.
I also would love to know what happens behind the doors when calls like this are made( how IO/ CPU resources are allocated for service/ API calls, what happens when a response is received).
====================Edit / More Info (For clarity)=====================
The client app making the API request is an ASP.NET windows service. There are two copies of the App and each of the instances is running on separate servers (Server 1 and Server 2) as local services. The web API is also an ASP.NET app hosted on a different server as a local service.
API request goes here :
Also, none of the client app's instance stops running for any reason, the problem is that requests from Server A (Server B never faces such issue) suddenly stops getting to the API.
Further investigations after using Wireshark (https://www.wireshark.org/) to trace the request reveals that the API requests actually do not leave the app when this problem starts. However, upon restart of the app's instance in question, the requests are then being sent to the API.
.net api web-services asp.net-web-api request
asked Nov 12 '18 at 9:47
ImaxoImaxo
236
add a comment |
I have two instances of an app running on IIS. Both apps asynchronously calls a web API hosted on a different server (running as a local service). At a point, requests from just one of the apps stops getting to the API. Just to be sure the API is still reachable from the server where the app is hosted, I initiated calls to the API via Postman, and everything goes fine.
Not too clear as to what the issue is exactly, but I can only think based on my level of understanding, that the app could not get further CPU(IO) resource to push further requests to the API.
While my next move is to use a packet sniffer to see if I can trace the requests on the server, I need help on what exactly has gone wrong, what am I to look out for and possible solutions.
I also would love to know what happens behind the doors when calls like this are made( how IO/ CPU resources are allocated for service/ API calls, what happens when a response is received).
====================Edit / More Info (For clarity)=====================
The client app making the API request is an ASP.NET windows service. There are two copies of the App and each of the instances is running on separate servers (Server 1 and Server 2) as local services. The web API is also an ASP.NET app hosted on a different server as a local service.
API request goes here :
Also, none of the client app's instance stops running for any reason, the problem is that requests from Server A (Server B never faces such issue) suddenly stops getting to the API.
Further investigations after using Wireshark (https://www.wireshark.org/) to trace the request reveals that the API requests actually do not leave the app when this problem starts. However, upon restart of the app's instance in question, the requests are then being sent to the API.
.net api web-services asp.net-web-api request
asked Nov 12 '18 at 9:47
ImaxoImaxo
236
"While my next move is to use a packet sniffer to see if I can trace the requests on the server, I need help on what exactly has gone wrong, what am I to look out for and possible solutions." - no, do this first before asking for ideas because without seeing the TCP stream dump there are simply too many possible causes.
– Dai
Nov 12 '18 at 9:50
Alright, thought as much. I will do and provide feedback. Thanks
– Imaxo
Nov 12 '18 at 9:58
I added more info on my question (under the edit section)
– Imaxo
Nov 14 '18 at 8:47
add a comment |
I have two instances of an app running on IIS. Both apps asynchronously calls a web API hosted on a different server (running as a local service). At a point, requests from just one of the apps stops getting to the API. Just to be sure the API is still reachable from the server where the app is hosted, I initiated calls to the API via Postman, and everything goes fine.
Not too clear as to what the issue is exactly, but I can only think based on my level of understanding, that the app could not get further CPU(IO) resource to push further requests to the API.
While my next move is to use a packet sniffer to see if I can trace the requests on the server, I need help on what exactly has gone wrong, what am I to look out for and possible solutions.
I also would love to know what happens behind the doors when calls like this are made( how IO/ CPU resources are allocated for service/ API calls, what happens when a response is received).
====================Edit / More Info (For clarity)=====================
The client app making the API request is an ASP.NET windows service. There are two copies of the App and each of the instances is running on separate servers (Server 1 and Server 2) as local services. The web API is also an ASP.NET app hosted on a different server as a local service.
API request goes here :
Also, none of the client app's instance stops running for any reason, the problem is that requests from Server A (Server B never faces such issue) suddenly stops getting to the API.
Further investigations after using Wireshark (https://www.wireshark.org/) to trace the request reveals that the API requests actually do not leave the app when this problem starts. However, upon restart of the app's instance in question, the requests are then being sent to the API.
.net api web-services asp.net-web-api request
asked Nov 12 '18 at 9:47
ImaxoImaxo
236
I have two instances of an app running on IIS. Both apps asynchronously calls a web API hosted on a different server (running as a local service). At a point, requests from just one of the apps stops getting to the API. Just to be sure the API is still reachable from the server where the app is hosted, I initiated calls to the API via Postman, and everything goes fine.
Not too clear as to what the issue is exactly, but I can only think based on my level of understanding, that the app could not get further CPU(IO) resource to push further requests to the API.
While my next move is to use a packet sniffer to see if I can trace the requests on the server, I need help on what exactly has gone wrong, what am I to look out for and possible solutions.
I also would love to know what happens behind the doors when calls like this are made( how IO/ CPU resources are allocated for service/ API calls, what happens when a response is received).
====================Edit / More Info (For clarity)=====================
The client app making the API request is an ASP.NET windows service. There are two copies of the App and each of the instances is running on separate servers (Server 1 and Server 2) as local services. The web API is also an ASP.NET app hosted on a different server as a local service.
API request goes here :
Also, none of the client app's instance stops running for any reason, the problem is that requests from Server A (Server B never faces such issue) suddenly stops getting to the API.
Further investigations after using Wireshark (https://www.wireshark.org/) to trace the request reveals that the API requests actually do not leave the app when this problem starts. However, upon restart of the app's instance in question, the requests are then being sent to the API.
.net api web-services asp.net-web-api request
.net api web-services asp.net-web-api request
asked Nov 12 '18 at 9:47
ImaxoImaxo
236
asked Nov 12 '18 at 9:47
ImaxoImaxo
236
edited Nov 12 '18 at 12:20
Imaxo
asked Nov 12 '18 at 9:47
ImaxoImaxo
236
asked Nov 12 '18 at 9:47
ImaxoImaxo
236
asked Nov 12 '18 at 9:47
ImaxoImaxo
236
236
"While my next move is to use a packet sniffer to see if I can trace the requests on the server, I need help on what exactly has gone wrong, what am I to look out for and possible solutions." - no, do this first before asking for ideas because without seeing the TCP stream dump there are simply too many possible causes.
– Dai
Nov 12 '18 at 9:50
Alright, thought as much. I will do and provide feedback. Thanks
– Imaxo
Nov 12 '18 at 9:58
I added more info on my question (under the edit section)
– Imaxo
Nov 14 '18 at 8:47
add a comment |
"While my next move is to use a packet sniffer to see if I can trace the requests on the server, I need help on what exactly has gone wrong, what am I to look out for and possible solutions." - no, do this first before asking for ideas because without seeing the TCP stream dump there are simply too many possible causes.
– Dai
Nov 12 '18 at 9:50
Alright, thought as much. I will do and provide feedback. Thanks
– Imaxo
Nov 12 '18 at 9:58
I added more info on my question (under the edit section)
– Imaxo
Nov 14 '18 at 8:47
"While my next move is to use a packet sniffer to see if I can trace the requests on the server, I need help on what exactly has gone wrong, what am I to look out for and possible solutions." - no, do this first before asking for ideas because without seeing the TCP stream dump there are simply too many possible causes.
– Dai
Nov 12 '18 at 9:50
"While my next move is to use a packet sniffer to see if I can trace the requests on the server, I need help on what exactly has gone wrong, what am I to look out for and possible solutions." - no, do this first before asking for ideas because without seeing the TCP stream dump there are simply too many possible causes.
– Dai
Nov 12 '18 at 9:50
Alright, thought as much. I will do and provide feedback. Thanks
– Imaxo
Nov 12 '18 at 9:58
Alright, thought as much. I will do and provide feedback. Thanks
– Imaxo
Nov 12 '18 at 9:58
I added more info on my question (under the edit section)
– Imaxo
Nov 14 '18 at 8:47
I added more info on my question (under the edit section)
– Imaxo
Nov 14 '18 at 8:47
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
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%2f53259501%2fwhat-are-the-possible-reasons-why-a-web-api-client-request-does-not-get-to-the-a%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
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%2f53259501%2fwhat-are-the-possible-reasons-why-a-web-api-client-request-does-not-get-to-the-a%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
"While my next move is to use a packet sniffer to see if I can trace the requests on the server, I need help on what exactly has gone wrong, what am I to look out for and possible solutions." - no, do this first before asking for ideas because without seeing the TCP stream dump there are simply too many possible causes.
– Dai
Nov 12 '18 at 9:50
Alright, thought as much. I will do and provide feedback. Thanks
– Imaxo
Nov 12 '18 at 9:58
I added more info on my question (under the edit section)
– Imaxo
Nov 14 '18 at 8:47