cancel
Showing results for 
Search instead for 
Did you mean: 

Activation fails in Integration Builder (Directory)

brian_arthern2
Participant
0 Kudos

Hi,

All of a sudden we have started to encounter the error below when we attempt to create/change and object and then activate it. This is PI 7.0 SP9

Any ideas?

javax.transaction.HeuristicMixedException: com.sap.engine.services.ts.exceptions.BaseHeuristicMixedException: One or more XAResources were not commited because of Exception in the second commit phase.

at com.sap.engine.services.ts.jta.impl.TransactionImpl.commit(TransactionImpl.java:432)

at com.sap.engine.services.ts.jta.impl.TransactionManagerImpl.commit(TransactionManagerImpl.java:319)

at com.sap.engine.services.ts.jta.impl.UserTransaction.commit(UserTransaction.java:79)

at com.sap.aii.ib.server.notification.AbstractMessageReceiver.commitMsgProcessingTx(AbstractMessageReceiver.java:223)

at com.sap.aii.ib.server.notification.AbstractMessageReceiver.onMessage(AbstractMessageReceiver.java:138)

at com.sap.jms.client.session.Session.run(Session.java:667)

at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)

at java.security.AccessController.doPrivileged(Native Method)

at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)

Caused by: javax.transaction.xa.XAException: XA operation cannot be completed successfully.

at com.sap.jms.client.xa.XAResource.commit(XAResource.java:47)

at com.sap.engine.services.jmsconnector.spi.ManagedSession$XAManagedResource.commit(ManagedSession.java:322)

at com.sap.engine.services.ts.jta.impl.ResourceList.commitTwoPhase(ResourceList.java:107)

at com.sap.engine.services.ts.jta.impl.TransactionImpl.commit(TransactionImpl.java:360)

... 9 more

Accepted Solutions (0)

Answers (3)

Answers (3)

brian_arthern2
Participant
0 Kudos

We actually did resolve it. We had an issue that the Oracle installation had initially been setup using local user accounts. In order to allow data protector to work we had to switch to domain user accounts.

What you need to do (assuming you have a similar situation) is enable read-write access of the home directory of the local oracle user to the domain user.

For some reason, unkonwn to man-kind (only known to SAP ) the system writes to this directory when activating configuration objects.

Former Member
0 Kudos

Hi,

I know this is not a professional solution, but y dont u guys try restarting the server or atleast J2EE engine.

-Naveen.

Former Member
0 Kudos

Hi Brian,

I got the same error. We are running NW2004s (XI 7.0) Sp9.

Have you gotten any feedback (email, etc) or have you find the solution ?

It seem to be a time-out error at the DB level (in the trace it is referring to XA – double phase commit)

Thank!

Unexpected error during message processing: javax.transaction.HeuristicMixedException: com.sap.engine.services.ts.exceptions.BaseHeuristicMixedException: One or more XAResources were not commited because of Exception in the second commit phase.

at com.sap.engine.services.ts.jta.impl.TransactionImpl.commit(TransactionImpl.java:432)

at com.sap.engine.services.ts.jta.impl.TransactionManagerImpl.commit(TransactionManagerImpl.java:319)

at com.sap.engine.services.ts.jta.impl.UserTransaction.commit(UserTransaction.java:79)

at com.sap.aii.ib.server.notification.AbstractMessageReceiver.commitMsgProcessingTx(AbstractMessageReceiver.java:223)

at com.sap.aii.ib.server.notification.AbstractMessageReceiver.onMessage(AbstractMessageReceiver.java:138)

at com.sap.jms.client.session.Session.run(Session.java:667)

at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)

at java.security.AccessController.doPrivileged(Native Method)

at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)

Caused by: javax.transaction.xa.XAException: XA operation cannot be completed successfully.

at com.sap.jms.client.xa.XAResource.commit(XAResource.java:47)

at com.sap.engine.services.jmsconnector.spi.ManagedSession$XAManagedResource.commit(ManagedSession.java:322)

at com.sap.engine.services.ts.jta.impl.ResourceList.commitTwoPhase(ResourceList.java:107)

at com.sap.engine.services.ts.jta.impl.TransactionImpl.commit(TransactionImpl.java:360)

brian_arthern2
Participant
0 Kudos

Hi Michel,

We actually did resolve it. We had an issue that the Oracle installation had initially been setup using local user accounts. In order to allow data protector to work we had to switch to domain user accounts.

What you need to do (assuming you have a similar situation) is enable read-write access of the home directory of the local oracle user to the domain user.

For some reason, unkonwn to man-kind (only known to SAP ) the system writes to this directory when activating configuration objects.

Hope this helps.. mail me if it does not as our Basis guys found this problem and may be able to help further...

Regards

Brian