JBoss EAP 6.2.0 and HornetQ - FIFO problem

[bpietraszuk]

Hi all,

Firstly, I would like to say that I know JMS is not designed for sequential/synchronized processing. However, I would like to know it is possible.

I have one queue with one producer (client application) and one consumer (MDB). I send 3 messages with IDs: 1,2,3, but MDB receives messages in incorrect order: 1,3,2. I have disabled MDB and check order in queue using QueueBrowser and order is correct (FIFO).

Could you please explain me why MDB receives messages in other order than I send them?

My MDB configuration:

@MessageDriven(activationConfig = {

        @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue"),

        @ActivationConfigProperty(propertyName = "destination", propertyValue = "java:jboss/exported/jms/queue/test"),       

        @ActivationConfigProperty(propertyName = "maxSession", propertyValue = "1"),

        @ActivationConfigProperty(propertyName="maxPoolSize", propertyValue="1"),

        @ActivationConfigProperty(propertyName="threadPoolMaxSize", propertyValue="1")})

Thank you in advance.

[clebert.suconic]

did you have maxSession at 1 when it happened?

When you have multiple sessions on the MDB you will have multiple instances consuming on multi-threads and you could have the impression of out of order because of that.

or do you have scheduled redelivery configured? if you cancel a message it may be scheduled to be redelivered after some time what would give you the out of order as well.

[bpietraszuk]

Hi,

thank you for your reply.

Yes, I have had maxSession set to 1.

I do not have sheduled redelivery at all.

Moreover, in JBoss logs I can see all messages are managed by one thread.

[jbertram]

As far as I know lots of users consume messages sequentially using the kind of approach you are using.  I would expect it to work.  Can you provide a reproducible test-case based on one of the Java EE examples we ship with HornetQ already?