[
https://issues.apache.org/activemq/browse/SM-1002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39961
]
Guillaume Nodet commented on SM-1002:
-------------------------------------
I think that if you allow more connections that the number of threads
available, you can not have any deadlock.
I would not remove the way to impose a maximum of connections per host if the
default settings are changed in a way that fix the problem (just setting them
to Integer.MAX should work). If the user need to have a max number of
connections, he could do so, knowing that the number of threads should be lower
(or unbounded, in which case all threads would wait for a free connection, but
this would not be very interesting)
> 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.
