Craig, Please let me know if my example project is not enough to investigate it and with some guidance from you I will try to provide something more appropriate.
Kind regards Artur Dorochowicz On 2 Cze, 21:55, Artur Dorochowicz <[email protected]> wrote: > I don't have a proper test case for this, but I created a > small,standalone project that shows this issue consistently. > It is available > athttps://sites.google.com/a/dorochowicz.com/artur-public-files/files-1... > There is a default/empty WCF service and an empty ASP MVC 2 > application with just the minimal amount of code (the only non > standard thing to open it are ASP.NET MVC 2 Tools for Visual Studio > 2008) > Start the Web app and refresh (manually) presented page 10 times, when > I try 11th time I get a timeout after 1 minute. > > Thanks Craig for taking the time to look at this issue. > > Best regards > > Artur Dorochowicz > > On 1 Cze, 22:45, Craig Neuwirt <[email protected]> wrote: > > > Certainly could be a bug some where. It would be great to somehow > > reproduce this in a test case if possible > > > On Jun 1, 2010, at 1:10 PM, Artur Dorochowicz wrote: > > > > Unless I'm doing something completely stupid then it is what I'm > > > seeing. > > > > When I look at IWindsorContainer.Kernel.ReleasePolicy.instance2Burden > > > in the debugger on subsequent requests I see that everything is > > > released fine except objects of type > > > Castle.Proxies.IWcfChannelHolderProxy (with burden > > > Castle.MicroKernel.Burden). When the number of leftover proxies > > > reaches 10 I start getting timeouts on service calls (since AFAIK 10 > > > is the default number of sessions in WCF services). > > > > I use official Windsor 2.1.1 and WCF facility build 48 (http:// > > > builds.castleproject.org/viewLog.html? > > > buildId=5633&tab=buildResultsDiv&buildTypeId=bt67) > > > > Let me know if I need to provide more details. > > > > Artur > > > > On 1 Cze, 13:32, Craig Neuwirt <[email protected]> wrote: > > >> If your client proxy is transient and injected into PWR component, it > > >> should get released at the end of each request. Are you saying this is > > >> not happening? > > > >> On May 31, 2010, at 12:50 PM, Artur Dorochowicz wrote: > > > >>> Hello, > > > >>> Due to the fact that WCF facility has rather limited documentation > > >>> available, I'd like to ask here for some help about its usage on the > > >>> client side. > > > >>> My scenario is an ASP.NET MVC web application that uses a WCF service > > >>> for which I have the service contract. > > >>> Controller factory is based on Windsor - controllers are resolved and > > >>> released by Windsor. > > >>> I have the configuration in web.config and configure the service like > > >>> this: > > > >>> AddFacility<WcfFacility>(); > > >>> Register( > > >>> Component.For<IMyWcfService>() > > >>> .ActAs( DefaultClientModel.On( > > > >>> WcfEndpoint.FromConfiguration( "name_of_configuration_in_web_config" ) > > >>> ) ) ); > > > >>> Is it correct? And what benefits does the WCF facility offer me on the > > >>> client side? > > > >>> This configuration seems to work correctly as long as the resolved > > >>> service client proxy is a dependency of transient components. But when > > >>> it becomes a dependency of component with PerWebRequest lifestyle, the > > >>> proxy seems to never be released, and after a couple of web requests I > > >>> reach a limit of connections/clients on the service side and I start > > >>> getting timeouts on calls to the service. > > >>> Is such scenario supported? Am I doing something wrong? > > > >>> Best regards > > > >>> Artur Dorochowicz > > > >>> -- > > >>> You received this message because you are subscribed to the Google > > >>> Groups "Castle Project Users" group. > > >>> To post to this group, send email to > > >>> [email protected]. > > >>> To unsubscribe from this group, send email to > > >>> [email protected]. > > >>> For more options, visit this group > > >>> athttp://groups.google.com/group/castle-project-users?hl=en. > > > > -- > > > You received this message because you are subscribed to the Google Groups > > > "Castle Project Users" group. > > > To post to this group, send email to > > > [email protected]. > > > To unsubscribe from this group, send email to > > > [email protected]. > > > For more options, visit this group > > > athttp://groups.google.com/group/castle-project-users?hl=en. -- You received this message because you are subscribed to the Google Groups "Castle Project Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/castle-project-users?hl=en.
