on 12-09-2008 10:45 AM
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
Hi,
Thanks very much for the quick response. We will try a work around in the mean time.
Regards Jaco
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
81 | |
25 | |
12 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.