Announcement Announcement Module
Collapse
No announcement yet.
Best effort 1 phased commit with the SimpleMessageListenerContainer Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • Best effort 1 phased commit with the SimpleMessageListenerContainer

    Hi,

    I want to implement a best effort 1PC with JPA and RabbitMQ and from what I understand I should simply pass the transaction manager to the SMLC during setup and it will use the JPA transaction manager.

    I noticed a big impact on the performance of the messaging because it's creating a new transaction every time it polls for a new message. is this correct ?

    If so, can I configure it too not do that and only create a transaction when it receives a message? Or should I create my own message listener which polls for a message, and if it receives one, creates the transaction and calls the MessageListenerAdapter to transform and pass it to my service? Are there any plans to create such a message listener container or should I continue on creating it?

  • #2
    big impact on the performance of the messaging
    It's not a big impact; there's no interaction with the DB when starting the transaction; it's just internal, in-memory stuff.

    Comment

    Working...
    X