[
https://issues.apache.org/activemq/browse/AMQ-2033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-2033.
-----------------------------
Resolution: Fixed
I added a close to the original commit so the close (same as your second patch)
is currently on trunk: see the
[diff|http://svn.apache.org/viewvc/activemq/trunk/activemq-core/src/main/java/org/apache/activemq/ActiveMQMessageProducer.java?p2=%2Factivemq%2Ftrunk%2Factivemq-core%2Fsrc%2Fmain%2Fjava%2Forg%2Fapache%2Factivemq%2FActiveMQMessageProducer.java&p1=%2Factivemq%2Ftrunk%2Factivemq-core%2Fsrc%2Fmain%2Fjava%2Forg%2Fapache%2Factivemq%2FActiveMQMessageProducer.java&r1=727353&r2=727352&view=diff&pathrev=727353]
Re the thread usage, and thread per producer. Please open another issue for
that as SystemUsage may need a little refactor to obtain a thread pool or
executor reference.
> 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, 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.
