Options for working around 60 second idle connection LB timeout

The LB times out idle connections after 60 seconds. There are several ways to work around this such as async work, chunked transfer, and ReliableSession, but there are no samples showing how to implement in ASP.NET and WCF.

57 votes

Vote 0 votes Vote Vote

Vote

Your email address

Check!

invalid email

(thinking…)

Reset

or sign in with

UserVoice password

Forgot password?

Create a password

Your name

I agree to the terms of service

You'll receive a confirmation email with a link to create a password (optional).

Signed in as (Sign out)

(thinking…)

Kevin Williamson shared this idea · Feb 23, 2011 · Flag idea as inappropriate… · Admin →

5 comments

Add a comment…

Your email address

Check!

invalid email

(thinking…)

Reset

or sign in with

UserVoice password

Forgot password?

Create a password

Your name

I agree to the terms of service

You'll receive a confirmation email with a link to create a password (optional).

Signed in as (Sign out)

Submitting...

Alex Jexler commented · Nov 16, 2011 1:00 am · Flag as inappropriate · Delete

Pls advice us in this question
John Falcon commented · Nov 16, 2011 12:55 am · Flag as inappropriate · Delete

The same problem. Weird, strange and unpleasant restriction. Hope that will be fixed soon.
Poul Allen commented · Nov 16, 2011 12:50 am · Flag as inappropriate · Delete

It would be nice to fix this restriction
hh commented · Jun 19, 2011 10:30 am · Flag as inappropriate · Delete

for this limitation, many real-world business application could not migrate to azure.
STonstad commented · Feb 23, 2011 3:00 pm · Flag as inappropriate · Delete

this is a huge pain point working with Azure!