[IGNITE-4763] doSetRollbackOnly method to be implemented in SpringTransactionManager

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.8
• Fix Version/s: 2.1
• Component/s: spring
• Labels: newbie patch
• Flags: Patch
• External issue URL: http://apache-ignite-users.70518.x6.nabble.com/SpringTransactionManager-Participating-in-existing-transactions-is-not-supported-td7305.html#a10624
• Assignee: Nikita Amelchev
• Reporter: Sumanta Ghosh
• Created: 01/Mar/17 03:55
• Updated: 04/Dec/17 08:27
• Resolved: 22/May/17 13:24

Description

This issue is raised in continuation with the message posted in ignite user forum (http://apache-ignite-users.70518.x6.nabble.com/SpringTransactionManager-Participating-in-existing-transactions-is-not-supported-td7305.html#a10624). Since the doSetRollBackOnly method is not implemented in SpringTransactionManager, it is not being possible to integrate with spring data's ChainedTransactionManager class. A simple fix (below) would work it seems (however, I did not yet tested with proper rollback test cases though, this implementation at least get rid of the exception chainedtransaction manager raises)

@Override
protected void doSetRollbackOnly(DefaultTransactionStatus status) throws TransactionException

{ Transaction txn = ((Ignite)this.getResourceFactory()).transactions().tx(); if (txn!=null) txn.setRollbackOnly(); }

NOTE: This is the first time I am raising issues in apache. So, apologies if all the details are not proper.

Issue Links

• links to: GitHub Pull Request #1884