After .NET 4.7 installation the webservice request timeout exception

Question

1.00/5 (1 vote)

See more:

, +

We have an application, which makes a webservice request to our application server.

The webservice request were working fine with .net 4.5 and 4.6, however after upgrading .net to 4.7 the same webservice request times out. We have not done any code changes in our application between upgrade to .net 4.6 and 4.7. The webservice request timeout is set 15 seconds configure in config file.

What I have tried:

If we set to 30 seconds the webservice request is successful. Not able to understand what is missing that a longer time makes request successful.

Posted 4-Sep-17 1:49am

Member 11665245

Updated 4-Sep-17 3:08am

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Graeme_Grant · Answer 1 · 2017-09-04T03:08:00

Solution 1

Have you tried breaking the key code to a separate app - one for each framework version - each identical. Then run tests, add & remove debugging info.

Have you tried Googling to see if others have experienced the same and found reasons why + workarounds? If it is a known problem, there will be noise. Otherwise, if not, then there may be an issue in your code.

Posted 4-Sep-17 3:08am

Graeme_Grant

Comments

[no name] 5-Sep-17 1:37am

Breaking key code also not work. This problem occur only on some systems but other system with same configuration and OS has no issue.

Graeme_Grant 5-Sep-17 1:46am

If you look at the information supplied to date, no source code showing WHERE it is breaking, we can only guess.

Programming is the art of problem-solving through code. You have a debugger and all the tools required at your disposal, you need to work through the problem using them.

I have given you a diagnostic process, time for you to roll up your sleeves and get dirty. You need to work on it and not say "it does not work". Break it down, identify, fix.