[
https://issues.apache.org/jira/browse/AMQ-1853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13187547#comment-13187547
]
Per Steffensen commented on AMQ-1853:
-------------------------------------
It is nice that there will finally be done something about this problem,
eventhough I am not sure exactly that it is the same problem as I have been
struggling with. This issue talks about the problem occuring if just on message
is to be redelivered. The problem I have, only completely blocks delivery of
new fresh messages, when there is more than maxMessagesPerSessions *
maxSessions messages waiting for redelivery on the same consumer at the same
time. I am using MDBs in Glassfish v2.1 as the consumer - maybe that makes the
difference. For those with access - see more on
https://fusesource.com/issues/browse/DEV-2279.
Will this fix also solve my problem?
Regards, Per Steffensen
> Optional non-blocking redelivery
> --------------------------------
>
> Key: AMQ-1853
> URL: https://issues.apache.org/jira/browse/AMQ-1853
> Project: ActiveMQ
> Issue Type: Wish
> Components: Broker
> Affects Versions: 5.1.0
> Reporter: Demian Mrakovich
> Assignee: Timothy Bish
> Fix For: 5.6.0
>
> Attachments: AMQ1853Test.java
>
>
> When a message is redelivered the consumer blocks for the amount of time
> specified by the redelivery delay. For a high load scenario where message
> order is irrelevant this is just reducing performance and will result in a
> complete halt if the delay is long and several bad messages are consumed in a
> short time.
> I think what I basically wish for is how it worked in versions 3.x, prior to
> fix for AMQ-268. So I would very much like to have configurable option to NOT
> block consumers when redelivering messages.
> If no-one feels up to it, I'd still appreciate some hints and I could try to
> fix it myself. Looking at ActiveMQMessageConsumer.rollback(), I was thinking
> something in the lines of just scheduling a task to put the message back on
> queue after a delay - if configured to, instead of stopping delivery and a
> schedule a task to resume delivery again. But I do not possess an
> understanding of AMQ thorough enough to predict potential side effects of
> this, so any analysis would be helpful.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
