[
https://issues.apache.org/activemq/browse/SM-1002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39957
]
Thomas Termin commented on SM-1002:
-----------------------------------
Bruce,
The problem seems to be in the ProviderProcessor:
You can test this with the following scenario for example:
httpclient -> consumer -> lwcontainer1 -> provider -> NETWORK -> consumer ->
lwcontainer2(with sleep of maybe 10sec)
The httpclient has to send more requests in a loop then you have max
connections per host.
What happens is all threads (higher then max connections per host) are on lock
to get a connection. If the first answer comes back there are no more threads
to bring the answer back. And then you have the hang/deadlock. The http
connection is closed after the done is initiated for the exchange. If the
answer is not processed the done state will never initiated and the connection
will not be closed and all other threads wait forever.
To solve this there should be something like if the threads are don't get a
connection, they should go back to the pool and the request should be queued.
If there is a connection available the next request from the queue can be
processed.
Any thoughts on this?
> 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.
