Timeout parameter at WCF web.config file does not affect/work on server
up vote
0
down vote
favorite
I have a WCF project. I am calling X service from my WCF service. When I call this X service it is waiting and responds after 3 minutes.
I want to increase timeout because default is 1 minute. When I add the config shown below to my local environment, it works.
But when I deploy this to the test environment, it is not working and I am getting timeout.
web.config:
<binding name="WSHttpBinding_ISyncReply"
openTimeout="00:01:00" closeTimeout="00:01:00"
receiveTimeout="00:10:00" sendTimeout="00:10:00">
I even added this config here to code behind, but it did not work either:
((IContextChannel)compClient.InnerChannel).OperationTimeout = new TimeSpan(0, 30, 0);
wcf timeout
edited Nov 9 at 15:47
marc_s
566k12610921245
asked Nov 9 at 15:03
mocco
7519
add a comment |
up vote
0
down vote
favorite
I have a WCF project. I am calling X service from my WCF service. When I call this X service it is waiting and responds after 3 minutes.
I want to increase timeout because default is 1 minute. When I add the config shown below to my local environment, it works.
But when I deploy this to the test environment, it is not working and I am getting timeout.
web.config:
<binding name="WSHttpBinding_ISyncReply"
openTimeout="00:01:00" closeTimeout="00:01:00"
receiveTimeout="00:10:00" sendTimeout="00:10:00">
I even added this config here to code behind, but it did not work either:
((IContextChannel)compClient.InnerChannel).OperationTimeout = new TimeSpan(0, 30, 0);
wcf timeout
edited Nov 9 at 15:47
marc_s
566k12610921245
asked Nov 9 at 15:03
mocco
7519
1
Simple rule of thumb, Server controls SendTimeout, client controls RecieveTiemout.
– mahlatse
Nov 13 at 19:25
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I have a WCF project. I am calling X service from my WCF service. When I call this X service it is waiting and responds after 3 minutes.
I want to increase timeout because default is 1 minute. When I add the config shown below to my local environment, it works.
But when I deploy this to the test environment, it is not working and I am getting timeout.
web.config:
<binding name="WSHttpBinding_ISyncReply"
openTimeout="00:01:00" closeTimeout="00:01:00"
receiveTimeout="00:10:00" sendTimeout="00:10:00">
I even added this config here to code behind, but it did not work either:
((IContextChannel)compClient.InnerChannel).OperationTimeout = new TimeSpan(0, 30, 0);
wcf timeout
edited Nov 9 at 15:47
marc_s
566k12610921245
asked Nov 9 at 15:03
mocco
7519
I have a WCF project. I am calling X service from my WCF service. When I call this X service it is waiting and responds after 3 minutes.
I want to increase timeout because default is 1 minute. When I add the config shown below to my local environment, it works.
But when I deploy this to the test environment, it is not working and I am getting timeout.
web.config:
<binding name="WSHttpBinding_ISyncReply"
openTimeout="00:01:00" closeTimeout="00:01:00"
receiveTimeout="00:10:00" sendTimeout="00:10:00">
I even added this config here to code behind, but it did not work either:
((IContextChannel)compClient.InnerChannel).OperationTimeout = new TimeSpan(0, 30, 0);
wcf timeout
wcf timeout
edited Nov 9 at 15:47
marc_s
566k12610921245
asked Nov 9 at 15:03
mocco
7519
edited Nov 9 at 15:47
marc_s
566k12610921245
asked Nov 9 at 15:03
mocco
7519
edited Nov 9 at 15:47
marc_s
566k12610921245
edited Nov 9 at 15:47
marc_s
566k12610921245
edited Nov 9 at 15:47
marc_s
566k12610921245
566k12610921245
asked Nov 9 at 15:03
mocco
7519
asked Nov 9 at 15:03
mocco
7519
asked Nov 9 at 15:03
mocco
7519
7519
1
Simple rule of thumb, Server controls SendTimeout, client controls RecieveTiemout.
– mahlatse
Nov 13 at 19:25
add a comment |
1
Simple rule of thumb, Server controls SendTimeout, client controls RecieveTiemout.
– mahlatse
Nov 13 at 19:25
1
1
Simple rule of thumb, Server controls SendTimeout, client controls RecieveTiemout.
– mahlatse
Nov 13 at 19:25
Simple rule of thumb, Server controls SendTimeout, client controls RecieveTiemout.
– mahlatse
Nov 13 at 19:25
add a comment |
1 Answer
1
active
oldest
votes
up vote
1
down vote
accepted
In my opinion, the reason may be that the binding configuration has not been applied to the client-side. try to add the binding configuration name to the client endpoint.
https://docs.microsoft.com/en-us/dotnet/framework/wcf/feature-details/configuring-timeout-values-on-a-binding
Besides, Are you sure that changing the client configuration will remove the timeout limit? I think we’d better change the binding configuration from the server.
answered Nov 12 at 9:24
Abraham Qian
4966
Yes, I used SOAP UI and i did not think there is timeout property in SOAP UI. I set timeout in SOAP UI and it works. Thank you very much your response.
– mocco
Nov 14 at 6:14
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
accepted
In my opinion, the reason may be that the binding configuration has not been applied to the client-side. try to add the binding configuration name to the client endpoint.
https://docs.microsoft.com/en-us/dotnet/framework/wcf/feature-details/configuring-timeout-values-on-a-binding
Besides, Are you sure that changing the client configuration will remove the timeout limit? I think we’d better change the binding configuration from the server.
answered Nov 12 at 9:24
Abraham Qian
4966
Yes, I used SOAP UI and i did not think there is timeout property in SOAP UI. I set timeout in SOAP UI and it works. Thank you very much your response.
– mocco
Nov 14 at 6:14
add a comment |
up vote
1
down vote
accepted
In my opinion, the reason may be that the binding configuration has not been applied to the client-side. try to add the binding configuration name to the client endpoint.
https://docs.microsoft.com/en-us/dotnet/framework/wcf/feature-details/configuring-timeout-values-on-a-binding
Besides, Are you sure that changing the client configuration will remove the timeout limit? I think we’d better change the binding configuration from the server.
answered Nov 12 at 9:24
Abraham Qian
4966
Yes, I used SOAP UI and i did not think there is timeout property in SOAP UI. I set timeout in SOAP UI and it works. Thank you very much your response.
– mocco
Nov 14 at 6:14
add a comment |
up vote
1
down vote
accepted
up vote
1
down vote
accepted
In my opinion, the reason may be that the binding configuration has not been applied to the client-side. try to add the binding configuration name to the client endpoint.
https://docs.microsoft.com/en-us/dotnet/framework/wcf/feature-details/configuring-timeout-values-on-a-binding
Besides, Are you sure that changing the client configuration will remove the timeout limit? I think we’d better change the binding configuration from the server.
answered Nov 12 at 9:24
Abraham Qian
4966
In my opinion, the reason may be that the binding configuration has not been applied to the client-side. try to add the binding configuration name to the client endpoint.
https://docs.microsoft.com/en-us/dotnet/framework/wcf/feature-details/configuring-timeout-values-on-a-binding
Besides, Are you sure that changing the client configuration will remove the timeout limit? I think we’d better change the binding configuration from the server.
answered Nov 12 at 9:24
Abraham Qian
4966
edited Nov 12 at 9:42
answered Nov 12 at 9:24
Abraham Qian
4966
answered Nov 12 at 9:24
Abraham Qian
4966
answered Nov 12 at 9:24
Abraham Qian
4966
4966
Yes, I used SOAP UI and i did not think there is timeout property in SOAP UI. I set timeout in SOAP UI and it works. Thank you very much your response.
– mocco
Nov 14 at 6:14
add a comment |
Yes, I used SOAP UI and i did not think there is timeout property in SOAP UI. I set timeout in SOAP UI and it works. Thank you very much your response.
– mocco
Nov 14 at 6:14
Yes, I used SOAP UI and i did not think there is timeout property in SOAP UI. I set timeout in SOAP UI and it works. Thank you very much your response.
– mocco
Nov 14 at 6:14
Yes, I used SOAP UI and i did not think there is timeout property in SOAP UI. I set timeout in SOAP UI and it works. Thank you very much your response.
– mocco
Nov 14 at 6:14
add a comment |
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%2f53228231%2ftimeout-parameter-at-wcf-web-config-file-does-not-affect-work-on-server%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
1
Simple rule of thumb, Server controls SendTimeout, client controls RecieveTiemout.
– mahlatse
Nov 13 at 19:25