Search code examples
javajakarta-eejmsmessage-driven-bean

Message Driven Bean and message consumption order

I have an MDB that gets subscribed to a topic which sends messages whose content is eventually persisted to a DB.

I know MDBs are pooled, and therefore the container is able to handle more than one incoming message in parallel. In my case, the order in which those messages are consumed (and then persisted) is important. I don't want an MDB instance pool to consume and then persist messages in a different order as they get published in the JMS topic.

Can this be an issue? If so, is there a way of telling the container to follow strict incoming order when consuming messages?

Solution

  • Copied from there:

    To ensure that receipt order matches the order in which the client sent the message, you must do the following:

    • Set max-beans-in-free-pool to 1 for the MDB. This ensures that the MDB is the sole consumer of the message.

    • If your MDBs are deployed on a cluster, deploy them to a single node in the cluster, [...].

    • To ensure message ordering in the event of transaction rollback and recovery, configure a custom connection factory with MessagesMaximum set to 1, and ensure that no redelivery delay is configured. For more information see [...].