Announcement Announcement Module
No announcement yet.
JDBC, transactions, good practices Page Title Module
Move Remove Collapse
Conversation Detail Module
  • Filter
  • Time
  • Show
Clear All
new posts

  • JDBC, transactions, good practices

    Hello all,

    I'm afraid that I miss some good practices in terms of handling database transactions with spring integration.

    I use JDBC backed queues, pollers and some other components. Sometimes I can notice stale data left in tables used for backing the queues (GROUP_TO_MESSAGE andd MESSAGE_GROUP). It's so rare, that I have no idea how to reproduce this.
    I can only suspect, that this is due to incorrect transaction handling.

    Can someone please provide some simple xml context file which makes use of spring managed jdbc transactions?

    I'm especially interested in example with poller, that consumes data from JDBC backed queue and in case of any errors will revert the transaction, so data consumed from queue will not be lost.