On Sep 4, 7:54 am, Fred <F...@discussions.microsoft.com> wrote:
> We are currently facing an issue with .Net Remoting connected application,
> here is the situation:
>
> We have a central server running some windows services who host some
> components exposed with .Net Remoting.
>
> One of them receive lot of calls, an average of 50 calls per second; it
> seems that when we go over that amount, it's an average, the service stop
> responding to the client's requests. We receive the following message "No
> connection could be made because the target machine actively refused it" just
> like when a service is not running or badly configured.
>
> It's important to know that when we receive the error message, the CPU usage
> of
> the server is no more than 50% meaning the CPU isn't overloaded.
>
> We have tried to increase the thread pool maximum count but that has no
> effect.
> Its look like the .Net Remoting call queue is full and cannot accept more
> requests.
>
> Is there somebody knowing if there is a limit in term of calls to a .Net
> remoting?
>
> Can we change that limit? Or something that can help us ?
>
> Many Thanks
>
> Fred

> Remoting calls are serviced on the threadpool, and I have seen thread
> starvation before. That being said, I can't remember if there was a
> hard limit for the number of simultaneous remoting calls.
>
> That being said, If your service is receiving 50 calls per second, it
> sounds like your remoting interface is a little chatty. (unless, of
> course, you have 50 clients accessing it at one call per second <g>)
>

On Sep 5, 4:12 am, Fred <F...@discussions.microsoft.com> wrote:
> > Remoting calls are serviced on the threadpool, and I have seen thread
> > starvation before. That being said, I can't remember if there was a
> > hard limit for the number of simultaneous remoting calls.
>
> > That being said, If your service is receiving 50 calls per second, it
> > sounds like your remoting interface is a little chatty. (unless, of
> > course, you have 50 clients accessing it at one call per second <g>)
>
> We have currently more than 400 clients concurrently connected to the
> service and sometimes we go over 70 calls second. It's a huge amount clearly
> but before starting a split of the services i want to know if I m really
> reaching a limit or if I still have something to do to solve the current
> issue. I had myself not see a limit somewhere in the doc and before we reach
> that huge amount of clients we had never facing that kind of issue (hopefully
> for us, the amount of clients still increasing ;-) ).

"Fred" <Fred@discussions.microsoft.com> wrote in message
news:2846D0BD-809A-45B4-999C-E4EB840C3A66@microsoft.com...
>
> We are currently facing an issue with .Net Remoting connected application,
> here is the situation:
>
> We have a central server running some windows services who host some
> components exposed with .Net Remoting.
>
> One of them receive lot of calls, an average of 50 calls per second; it
> seems that when we go over that amount, it¡¯s an average, the service stop
> responding to the client¡¯s requests. We receive the following message
> ¡°No
> connection could be made because the target machine actively refused it¡±
> just
> like when a service is not running or badly configured.
>
> It¡¯s important to know that when we receive the error message, the CPU
> usage
> of
> the server is no more than 50% meaning the CPU isn¡¯t overloaded.
>
> We have tried to increase the thread pool maximum count but that has no
> effect.
> Its look like the .Net Remoting call queue is full and cannot accept more
> requests.
>
> Is there somebody knowing if there is a limit in term of calls to a .Net
> remoting?
>
> Can we change that limit? Or something that can help us ?
>
> Many Thanks
>
> Fred