[jboss-user] [Remoting] - Re: Problem with backlog queue behavior ?

2008-04-22 Thread [EMAIL PROTECTED]
"nicolas.medoc" wrote : | Ok, there is sense to have clientMaxPoolSize<=maxpoolSize. But in this case I should expect that the backlog queue don't be used. So I wonder about the responsability of backlog queue. In what situation is it used ? Well, SocketServerInvoker will stop accepting conne

[jboss-user] [Remoting] - Re: Problem with backlog queue behavior ?

2008-02-22 Thread nicolas.medoc
Hi Ron, Thanks for your response. When the clientMaxPoolSize=MaxPoolSize=100, all the 300 client threads works fine - only for the threads that don't reach numberOfRetries=30 (corresponding to a time of 30 seconds). Ok, there is sense to have clientMaxPoolSize<=maxpoolSize. But in this case I

[jboss-user] [Remoting] - Re: Problem with backlog queue behavior ?

2008-02-07 Thread [EMAIL PROTECTED]
Hi Nicolas, Couple of points: 1. clientMaxPoolSize=50 means that there can never be more than 50 simultaneous invocations from a given client. 2. maxPoolSize=400 means that there can never be more than 400 simultaneous invocations on the server. 3. 1) and 2) imply that, in your first exampl

[jboss-user] [Remoting] - Re: Problem with backlog queue behavior ?

2008-01-18 Thread nicolas.medoc
Finally I have downloaded the 4.2.2 version of JBoss and the 2.2.2.SP3 version of Remoting. I have proceed with the same approach as previously, using the folowing configuration : | |${jboss.bind.address} |3873 |400 |