IIS 7 and Above
Last post Jul 14, 2015 06:03 PM by Rovastar
Jul 14, 2015 02:42 PM|intiko81|LINK
I am trying to find a solution to limit the number of instanciated IIS pipelines. I am on it for almost two week already. I want to undserstand why IIS instanciate randomly a new pipeline (as needed). How can we fix that number? In high traffics, it could
easily reach 100+ pipelines.
I am on Windows server 2012 so I guess it's IIS 8.0.
Jul 14, 2015 03:20 PM|Rovastar|LINK
I have never worried about the amount of pipelines and never even looked at it.
What problem are you trying to solve?
Jul 14, 2015 04:43 PM|intiko81|LINK
It interfers with my application design. I have a web service (could be aspnet web site too) and each request to asmx (or aspx), a new pipeline could be created. All my asmx (or aspx) point to a singleton (main entry to handle a request). This singleton
is [ThreadStatic] so each pipeline created has his own instance of the application, which means each instance will have its own connection to DB all the way down. Each db connection is opened and stays open for the lifetime of the instance, here a pipelnie.
I want to limit these number of connections
It seems that older versions of IIS in classic mode have a limited number of pipelines.
Please feel free to ask more details.
Jul 14, 2015 06:03 PM|Rovastar|LINK
It sounds like you need connection pools.
But really the developer question are better asked for the forums.asp.net