[
https://issues.apache.org/activemq/browse/SM-1002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39959
]
Thomas Termin commented on SM-1002:
-----------------------------------
So if I understand you correctly then you will limit the number of connections
with the number of threads. I will try this out. But you have to remove the
opportunity for the user to change the values for max connections and max
connections per host. Because If you don't do that the user can again configure
a deadlock scenario, right?
> 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.
