Home/ Questions/Q 8533447
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-11T09:58:01+00:00

Assume some spring bean has transactional method and it does two things: asynchronously send

  • 0

Assume some spring bean has transactional method and it does two things:

  • asynchronously send JMS messages
  • updates DB

The problem is that when the message is consumed, the DB transaction sometimes not have committed, and handler failed to find in DB expected value.

The evident solution – is to send in transaction, but I use async send available on ActiveMQ to increase throughput. If I make send transactional, I forfeit asynchrocity and also risk getting OuOfMemory.

How would you solve this problem?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    You need to use an XA-enabled transaction manager, and send the JMS message and do the update to the DB in the same, distributed transaction.

    This doesn’t change anything to asynchronicity: the send call will return before the receiver receives the message. But when it receives it, the transaction will be committed, and the receiver will find the updates in the database.

    I don’t see what OutOfMemoryErrors have to do with this.

    • 0