activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tamas Cserveny (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMQ-5400) Unable to keep message order using ActiveMQ-RAR
Date Wed, 22 Oct 2014 18:11:33 GMT

     [ https://issues.apache.org/jira/browse/AMQ-5400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Tamas Cserveny updated AMQ-5400:
--------------------------------
    Attachment: block-session-until-redelivery.patch

Hi,

I've provided a patch which blocks the session for the time of the redelivery. It honours
the isNonBlockingRedelivery flag of the connection so it can be turned off. As blocking redelivery
is the default this should not be a problem.

Cheers,

Tamas

> Unable to keep message order using ActiveMQ-RAR 
> ------------------------------------------------
>
>                 Key: AMQ-5400
>                 URL: https://issues.apache.org/jira/browse/AMQ-5400
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 5.10.0
>         Environment: JBoss EAP6 + ActiveMQ 5.10.0
>            Reporter: Tamas Cserveny
>         Attachments: block-session-until-redelivery.patch
>
>
> We have an application server which processes the messages using an MDB.  We are using
message grouping to keep the message processing order.
> It seems that it is not possible to do this, because in case the onMessage signals rollback,
then the queue does not block until the redelivery time, but keeps on dispatching.
> ActiveMQSession.java method afterRollback() @938 is triggered in this case. Which will
redeliver the message by scheduling it:
> connection.getScheduler().executeAfterDelay(new Runnable() {
>                                     @Override
>                                     public void run() {
>                                         ((ActiveMQDispatcher)md.getConsumer()).dispatch(md);
>                                     }
>                                 }, redeliveryDelay);
> The session is not blocked or otherwise stopped from processing more messages, so it
does it.
> Setting prefetch=1 for the consumer did not helped.
> I have maxSessions=1 in the activationSpec.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message