Is Spring Integration transaction isolation serialized required or can I also use read committed?

Question

I using spring integration with JdbcChannelMessageStore backed up with postgres using pgbouncer. I have multiple jvms running, and got:

Could not serialize access due to concurrent delete (or update)

Is this a problem?
Can/should I switch to read committed (and if so, how)?

score 0 · Answer 1 · answered Jul 21 '22 at 14:12

The JdbcChannelMessageStore does not start transaction, it is just participate in the existing one. Look ho you start it on your service level. Perhaps it is just a @Transactional and it does have this option:

/**
 * The transaction isolation level.
 * <p>Defaults to {@link Isolation#DEFAULT}.
 * <p>Exclusively designed for use with {@link Propagation#REQUIRED} or
 * {@link Propagation#REQUIRES_NEW} since it only applies to newly started
 * transactions. Consider switching the "validateExistingTransactions" flag to
 * "true" on your transaction manager if you'd like isolation level declarations
 * to get rejected when participating in an existing transaction with a different
 * isolation level.
 * @see org.springframework.transaction.interceptor.TransactionAttribute#getIsolationLevel()
 * @see org.springframework.transaction.support.AbstractPlatformTransactionManager#setValidateExistingTransaction
 */
Isolation isolation() default Isolation.DEFAULT;

The Spring Integration transactions support options do provide hooks to configure it similar way: https://docs.spring.io/spring-integration/docs/current/reference/html/transactions.html#transactions

Thanks. Still wondering which transaction isolation level best to use. Given that the default repeatable_read gives errors. — wdk, Jul 21 '22 at 15:25
It probably depends on your vendor. So, just try other variants. — Artem Bilan, Jul 21 '22 at 15:27

wdk · Answer 2 · 2022-08-29T10:05:08.187

For a Poller it seems to be done like this:

  @Bean(MESSAGING_TRANSACTION_INTERCEPTOR)
    public static TransactionInterceptor transactionInterceptor() {
        return new TransactionInterceptorBuilder(true)
                .isolation(READ_COMMITTED) // The default ISOLATION_REPEATABLE_READ leads to errors and is not needed
                .build();
    }

    @Bean(name = DEFAULT_POLLER)
    public PollerMetadata pollerMetaData(@Qualifier(MESSAGING_TRANSACTION_INTERCEPTOR) TransactionInterceptor transactionInterceptor) {
        PollerMetadata meta = new PollerMetadata();
        meta.setAdviceChain(List.of(transactionInterceptor));
        return meta;
    }

Is Spring Integration transaction isolation serialized required or can I also use read committed?

2 Answers2