activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Danielius Jurna (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AMQ-2033) Deadlock on producerWindow.waitForSpace() in ActiveMQMessageProducer
Date Tue, 23 Dec 2008 17:27:05 GMT

    [ https://issues.apache.org/activemq/browse/AMQ-2033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=48318#action_48318
] 

Danielius Jurna commented on AMQ-2033:
--------------------------------------

Now with this patch, there is one thread for every producer created. On heavy systems, there
are big amount of threads created (hundreds) and waiting, because every producerWindow has
it's own thread executor. I thing they should reuse session thread pool or smth. Should I
create new issue for this?

> Deadlock on producerWindow.waitForSpace() in ActiveMQMessageProducer
> --------------------------------------------------------------------
>
>                 Key: AMQ-2033
>                 URL: https://issues.apache.org/activemq/browse/AMQ-2033
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.2.0
>            Reporter: Danielius Jurna
>            Assignee: Gary Tully
>            Priority: Critical
>             Fix For: 5.3.0
>
>         Attachments: producer.patch, ProducerFlowControlTest.java, ProducerFlowControlTest.patch
>
>
> It seems, that producer throttling with producerWindow enabled doesn't work at all. I'm
attaching unit test for this. After sending about ~80msg producer stops and never resumes
sending. 
> The problem is that producerWindow is not started ActiveMQMessageProducer. There must
be something like this:
> producerWindow.start();
> I'm also attaching patch for this bug

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


Mime
View raw message