cancel
Showing results for 
Search instead for 
Did you mean: 

netweaver 7.1 transactionmanager

Former Member
0 Kudos

Hi,

The application is running on netweaver ce 7.1. We are using spring to create/inject our service layer and using declarative transaction management. The resources are xa resources and we are using JTA transactionmanager.

In a particular scenario we have a transaction boundary that is demarcated as 'REQUIRES_NEW' because this this has to commit/rollback separate from the current transaction. The suspend bit seems to work, but when 'begin' is called on the new transaction, we get the following exception:

Caused by: javax.transaction.SystemException: It is not possible to enlist connections into different transaction if they are already enlisted into another transaction.

at com.sap.engine.services.connector.resource.impl.ResourceSetImpl.enlistAll(ResourceSetImpl.java:497)

at com.sap.engine.services.ts.jta.impl.UserTransaction.begin(UserTransaction.java:56)

at org.springframework.transaction.jta.JtaTransactionManager.doJtaBegin(JtaTransactionManager.java:886)

at org.springframework.transaction.jta.JtaTransactionManager.doBegin(JtaTransactionManager.java:843)

Does anybody have any ideas as to a possible solution?

Regards Jaco

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi,

Thanks very much for the quick response. We will try a work around in the mean time.

Regards Jaco

nikolai_tankov
Explorer
0 Kudos

Hi Jaco,

This is a known issue into transaction manager and the solution will be available in 7.10 SP8 and 7.11 SP2.

Currently the fix is available only internally in SAP.

In which release/SP you need this fix.

Best regards,

Nikolai.