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
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
|
hello
My JBoss version is 4.0.4GA. The JBoss Remoting version is 1.4.3 (I can see it
in boss-remoting.jar : meta-inf/manifest.mf).For testing my configuration, I
create 500 threads in my client. Each thread invoke an EJB method that simulate
an execution with Thread.sleep(time).
My configurati
My JBoss version is 4.0.4GA. In jboss-remoting.jar (in meta-inf/manifest.mf)
the specification version is 1.4.3. The default timeout is 180.
For this version, the timeout configuration don't work with "socketTimeout"
parameter but with "timeout" parameter. Like this :
| socket://0.0.0.0:
