HTTP connections and IIS6

Thanks for the reply David,
I've found a lot of Timer_ConnectionIdle calls in there towards the
end of the batch processing. Does that mean the application just isnt
using them? I definitely have 30 connections open because I make a
call in the ServicePointManager in my code to set it to 30 and you can
see them opening in performance monitor. If the frmaework is dropping
them is there any way I can keep them open?

Thanks for the advice

Ian

"David Wang [Msft]" <someone RemoveThis @online.microsoft.com> wrote in message news:<Opt6pJUnDHA.1728 RemoveThis @TK2MSFTNGP09.phx.gbl>...
 > Check %SYSTEMROOT%\System32\LogFiles\HTTPERR\*.log and see if there's lots
 > of connection failures there.
 >
 > .Net network classes pool their network connections, which can be
 > problematic depending on your usage. Are you sure you were actually getting
 > 30 concurrent HTTP connections?
 >
 > --
 > //David
 > IIS
 > This posting is provided "AS IS" with no warranties, and confers no rights.
 > //
 > "Ian L" <ianlawton RemoveThis @talk21.com> wrote in message
 > news:1be76897.0310270804.749e4c0c@posting.google.com...
 > Hi,
 > I have a C# web service application that runs on IIS 5 which is called
 > by a C# windows service repeatedly from two different machines. The
 > windows service opens 30 http connections to the web service and uses
 > them in parallel to process batches. These connections remain at 30
 > throughout the life of the processing. Recently I moved the web
 > service to a Windows 2003 IIS 6 machine and have the behaviour of the
 > application has changed. Regardless of the size of the batches, as
 > soon as it gets to within a couple of thousand to go the http
 > connections begin to reduce until it reaches a single connection.
 >
 > I have tried several different configurations changes on the IIS
 > machine (increasing the http timeout, changes to the application pool,
 > etc) but without success.
 >
 > Can anyone shed any light on this please?
 >
 >
 > Ian<!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: HTTP connections and IIS6 

It sounds like .Net Framework may have opened 30 on your behalf, but it's
only using very few of them (since it is pooling network connections behind
the scenes). So the extra ones opened but not used are all timing out due
to inactivity.

I'm not certain how you can force the .Net Framework to not pool network
connections -- but I think you should rethink your design. If you need 30
concurrent connections, you cannot use network classes that pool connections
on your behalf. Either you do not really need 30 concurrent connections, or
you use a different network class.

--
//David
IIS
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Ian L" <ianlawton.TakeThisOut@talk21.com> wrote in message
news:1be76897.0310290924.74f9d97@posting.google.com...
Thanks for the reply David,
I've found a lot of Timer_ConnectionIdle calls in there towards the
end of the batch processing. Does that mean the application just isnt
using them? I definitely have 30 connections open because I make a
call in the ServicePointManager in my code to set it to 30 and you can
see them opening in performance monitor. If the frmaework is dropping
them is there any way I can keep them open?

Thanks for the advice

Ian

"David Wang [Msft]" <someone.TakeThisOut@online.microsoft.com> wrote in message
news:<Opt6pJUnDHA.1728.TakeThisOut@TK2MSFTNGP09.phx.gbl>...
 > Check %SYSTEMROOT%\System32\LogFiles\HTTPERR\*.log and see if there's lots
 > of connection failures there.
 >
 > .Net network classes pool their network connections, which can be
 > problematic depending on your usage. Are you sure you were actually
getting
 > 30 concurrent HTTP connections?
 >
 > --
 > //David
 > IIS
 > This posting is provided "AS IS" with no warranties, and confers no
rights.
 > //
 > "Ian L" <ianlawton.TakeThisOut@talk21.com> wrote in message
 > news:1be76897.0310270804.749e4c0c@posting.google.com...
 > Hi,
 > I have a C# web service application that runs on IIS 5 which is called
 > by a C# windows service repeatedly from two different machines. The
 > windows service opens 30 http connections to the web service and uses
 > them in parallel to process batches. These connections remain at 30
 > throughout the life of the processing. Recently I moved the web
 > service to a Windows 2003 IIS 6 machine and have the behaviour of the
 > application has changed. Regardless of the size of the batches, as
 > soon as it gets to within a couple of thousand to go the http
 > connections begin to reduce until it reaches a single connection.
 >
 > I have tried several different configurations changes on the IIS
 > machine (increasing the http timeout, changes to the application pool,
 > etc) but without success.
 >
 > Can anyone shed any light on this please?
 >
 >
 > Ian<!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: HTTP connections and IIS6