[
https://issues.apache.org/activemq/browse/SM-1002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39958
]
Guillaume Nodet commented on SM-1002:
-------------------------------------
This is a good idea. The only problem is to make sure that if a connection is
freed, a job will be automatically dequeued. So this is really a list and we
need to manage it ourselves.
Another option is to remove the limitation on the max number of connections and
use the thread pool to control this. As there will be no more connections than
the number of threads at any time. Well, I guess for the newer endpoints this
is wrong because they are asynchronous, but ...
Btw, I think the total number of connections should be set very high in any
case, as this is more a system limitation.
And we need to move the thread pool configuration on a per endpoint basis
instead of per component imho.
So what if we put both limits to a very high number in the default
configuration ? Is there any drawbacks?
> Service mix hangs when the # concurrent requests exceeds the
> maxConnectionsPerHost
> ----------------------------------------------------------------------------------
>
> Key: SM-1002
> URL: https://issues.apache.org/activemq/browse/SM-1002
> Project: ServiceMix
> Issue Type: Bug
> Components: servicemix-core
> Environment: Unix, Java 1.5
> Reporter: Ruwan Linton
>
> When I am doing a performance test I have sent more than 40 concurrent
> requests from a single host to servicemix, and the maxConnectionsPerHost was
> 40. It is acceptable the failing to respond when it exceeds 40
> (maxConnectionsPerHost) concurrent requests.
> But afterward, SM hangs.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
