[ 
https://issues.apache.org/activemq/browse/SM-512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=43903#action_43903
 ] 

Guillaume Nodet commented on SM-512:
------------------------------------

Yeah, i know the problem comes from here, but the other solutions are to reject 
the work (which would mean the exchange is lost), or to have an unbounded 
thread pool (which may be problematic too).  The real solution is to get rid of 
the sendSync as much as possible, which should be possible in smx4, because the 
transaction model is changed and the use of sendSync is not required anymore to 
convey transactions.

> sendsync from a service to another service seems to cause a deadlock under 
> load
> -------------------------------------------------------------------------------
>
>                 Key: SM-512
>                 URL: https://issues.apache.org/activemq/browse/SM-512
>             Project: ServiceMix
>          Issue Type: Bug
>    Affects Versions: 3.0-M2
>         Environment: Windows 2003, Intel 2.8 xeon processor. Java 1.5 3.0-M2
>            Reporter: anand somani
>            Assignee: Guillaume Nodet
>             Fix For: 3.0
>
>         Attachments: test.zip
>
>
> We have 2 services A and B. A makes sync requests to B. We have a JMS client 
> that feeds requests to A and that triggers a sync request to B. We are trying 
> to push some 5000 requests (not sequential). Now
>      With st flow - A gets all the responses from B and we are good
>      with Seda flow -  A gets some responses from B (sometimes none) and then 
> all the threads are blocked (seen using JMX) on syncsend(), looks like B has 
> no threads to service requests.
>      with JMS flow ( A and B on different VMs), we see the similar behavior 
> as with seda flow
> With async requests everything works just fine. We have tried increasing seda 
> capacity and workmanager thread count, that did not help.  I am attaching 
> service A and B code along with configuration files
> Also it would be nice to have all the tunable features documented with some 
> explaination somewhere ( I could not find it anywhere)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to