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

Krzysztof Sobolewski commented on SM-512:
-----------------------------------------

And, BTW, it seems to me rather to be a special case of deadlock where a thread 
waits for itself. Notifying locks in this case is of no use, because notify 
works by waking up a thread that is already waiting, but you can't call notify 
from such a thread. Notifying before waiting has no effect. Then, I think, it 
simply should not wait :)

And, also:
> I'm wondering if there could be some cases under high load, where a single 
> thread is used

Yes, it is possible. Quoting http://servicemix.apache.org/thread-pools.html:
    *  if the number of threads is less than corePoolSize, the executor will 
create a new thread to handle the job
    * if the number of queued jobs is less than queueSize, the job is queued
    * if the queue is full and the number of threads is less than 
maximumPoolSize, a new thread is created to handle the job
    * else, the current thread will handle the job
It's the last point that is problematic.

> 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