Regarding distributed transaction

may be xi does not support distributed transaction. as 2 phase commit
really?
if yeah,and i have the question the following:
because as far as know, xi will create seperate transaction for each step.
and send step will influence the transactional behavior.
by checking help, i knew
we can set properties for send step not to start a new transaction.
can anybody tell me where to set that?
and then how can we assure transaction integrity.
if not 2 phase commit protocol, and with what to do it?

Hi ,
Please check this blog.
/people/sap.user72/blog/2005/10/15/jdbc-adapter-execution-mode-chained-or-unchained (JDBC Adapter execution mode Chained or Unchained )
Ranjeet Singh.

Similar Messages

Regarding Distributed Transactions

I am aware of JDBC transactions. Now while reading EJB i came to know that EJB supports Distributed Transactions.
My interpretation of Distributed transaction is
e.g.
Consider two CMT Beans A & B.
Bean-A contains a method foo() with a transaction attribute "Required".
Bean-B contains a method boo() with a transaction attribute "Required".
Now when a method "foo()" in a transaction calls method "boo()", the method "boo()" runs in the same transaction as "foo()". so here the transaction travels from "foo()" method to "boo()" method.
My Question: can i say the above is an example of Distributed transaction
Please let me know my interpretation is correct or wrong.
If wrong, please explain me in few words.

Hi Naresh,
Your interpretation is correct. Distributed transactions allow a transaction to propagate between
component invocations. Typically, this propagation occurs between components that are collocated
within the same JVM, but the propagation can also happen across JVMs, e.g. in the case of a
Remote EJB invocation.
--ken

Distributed Transaction in weblogic 5.1

Hi all,
Does Weblogic 5.1 support Distributed Transactions?.

While they aren't java-specific, if you're looking for XA/2PC details,
these 2 are good:
Transaction Processing: Concepts and Techniques (Morgan Kaufmann Series
in Data Management Systems)
by Jim Gray, Andreas Reuter
Principles of Transaction Processing
by Philip A. Bernstein, Eric Newcomer (Contributor)
5.1 does not support XA or 2 phase-commit. However, it does allow
multiple cluster members to enlist in the same transaction as long as
all database access goes through the same JDBC connection.
WLS 6.0 and later do support XA and 2PC.
-- Rob
chandrasekar wrote:
Hi all,
Does Weblogic 5.1 support Distributed Transactions?.Please suggest me some
books or documentation regarding Distributed Transactions, and about the XA compliant
resources.

Can not commit distributed transaction

Hi
We get error "can not commit distributed transaction" during
commit the transaction in which we have create NEW entities.
Update-transactions on existing enitites work correct.
Our problem is probably due to seauences for object IDs: we are using oracle native sequences:
<sequence name="SeqErrRecObj" strategy="nontransactional" factory-class="native(Sequence=BUYING.SEQ_ERRRECOBJ)"/>
As soon we use strategy="nontransactional" in managed environment,
we get "can not commit distributed transaction" error by creating new instance.
Switching to strategy="transactional" seems to eleminate this problem.
I did not found any hint in about this in documentation.
Can some one confirm our assumption that using nontransactional oracle sequences in manageg (WebLogic 9.2) environment
is responsible for "can not commit distributed transaction" error and "strategy=transactional" is the right solution.
Probably we are completely wrong and tehre is some other explanation for this error ?
kind regards
Andre Teshler

Hi Andre,
It sounds like you have not configured a non-transactional datasource. See section "4.2.1. Managed and XA DataSources" in the <kodo>/docs/jdo/pdf/manual.pdf. Connection is for the managed datasource and Connection2 for the non-transactional.
David Ezzio

Problem: [Microsoft][ODBC SQL Server Driver][SQL Server]The Microsoft Distributed Transaction Coordinator (MS DTC) has cancelled the distributed transaction.

Hi Gurus,
I have this problem in my MS SQL Server 2012 that is running in SQL Server 2008 R2 Enterprise 64 bit.. Not sure why... Here is the full details of the error:
Microsoft OLE DB Provider for ODBC Drivers 80040E14
[Microsoft][ODBC SQL Server Driver][SQL Server]The Microsoft Distributed Transaction Coordinator (MS DTC) has cancelled the distributed transaction.
/Libraries/DBA/DBA.asa, line 717
Line 717 is this:
rs.open destTableName,,,,adCmdTable
Full details of the code:
    'Field object used to iterate through each field of the rs
   dim rs, fld
   'call dbInitRS(rs)
   set rs = server.createobject("adodb.recordset")
   'On Error Resume Next
   'Open rs
   set rs.activeConnection = myConnection
   rs.cursorType = adOpenKeyset
   rs.lockType = adLockOptimistic
   'rs.open destTableName
   rs.open destTableName,,,,adCmdTable
   'if err.number <> 0 then
   '   goto HandleError
   'end if
   rs.addNew
Any ideas how to solve this problem?
Thanks

Still does not work. I have allow MSDSTC in my firewall list.
Hi dudskie,
Have you try to use DTCTester or DTCPing to verify MSDTC functionality over the network? Please refer to the following article:
Troubleshooting Problems with MSDTC:
http://msdn.microsoft.com/en-us/library/aa561924.aspx
Use the DTCTester utility to verify transaction support between two computers if SQL Server is installed on one of the computers. The DTCTester utility uses ODBC to verify transaction support against a SQL Server database. For more information about
DTCTester see How to Use DTCTester Tool.
Use DTCPing to verify transaction support between two computers if SQL Server is not installed on either computer. The DTCPing tool must be run on both the client and server computer and is a good alternative to the DTCTester utility when SQL Server
is not installed on either computer. For more information about DTCPing, see
How to troubleshoot MS DTC firewall issues.
If you have any feedback on our support, please click
here.
Hope this helps.
Regards,
Elvis Long
TechNet Community Support

How to disable distributed transaction in Weblogic 8.1?

          Hi I'm using WL8.1 running EJB. I wish to disable distributed transaction, whatever
          that is. It is preventing me from doing and AutoCommit(true) in my database. Please
          help. Thanks!


You cannot disable transactions if you are using entity EJBs but you can
          get your connections from a non-TX DataSource (just define a regular
          DataSource and not TXDataSource in your configuration) and then those
          connections will not be transaction aware so you'll be able to do
          setAutoCommit(true) in fact it might already be the default setting when
          you get the connection.
          Regards,
          Dejan
          Fred wrote:
          >Hi I'm using WL8.1 running EJB. I wish to disable distributed transaction, whatever
          >that is. It is preventing me from doing and AutoCommit(true) in my database. Please
          >help. Thanks!
          >
          >

Does Oracle 8.1.5 with weblogic 6.1 sp2 suppports Distributed Transactions ---A really night Mare

          Which version of jdbc thin driver should i use to achieve distributed transaction
          with oracle 8.1.5 in weblogic 6.1 sp2
          right now if iam using the driver classes provided in weblogic.jar iam gettig the
          following Exception
          AccountBean.ejbCreate( id = accountId, initial balance = $ 3000.0)
          java.sql.SQLException: XA error: XAER_RMERR : A resource manager error has occured
          in the transaction branch start(
          ) failed on resource 'OracleXAPool' Unexpected error during start for XAResource
          'OracleXAPool': null
          at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1044)
          at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1010)
          at weblogic.jdbc.jta.Connection.getXAConn(Connection.java:148)
          at weblogic.jdbc.jta.Connection.prepareStatement(Connection.java:226)
          at weblogic.jdbc.rmi.internal.ConnectionImpl.prepareStatement(ConnectionImpl.java:135)
          at weblogic.jdbc.rmi.SerialConnection.prepareStatement(SerialConnection.java:76)
          at examples.ejb.basic.beanManaged.AccountBean.ejbCreate(Unknown Source)
          at examples.ejb.basic.beanManaged.AccountBean_g1748h_Impl.ejbCreate(AccountBean_g1748h_Impl.java:172)
          at java.lang.reflect.Method.invoke(Native Method)
          at weblogic.ejb20.manager.DBManager.create(DBManager.java:492)
          at weblogic.ejb20.manager.DBManager.remoteCreate(DBManager.java:462)
          at weblogic.ejb20.internal.EntityEJBHome.create(EntityEJBHome.java:190)
          at examples.ejb.basic.beanManaged.AccountBean_g1748h_HomeImpl.create(AccountBean_g1748h_HomeImpl.java:76)
          at examples.ejb.basic.beanManaged.AccountBean_g1748h_HomeImpl_WLSkel.invoke(Unknown
          Source)
          at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:288)
          at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
          at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:257)
          at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:158)
          at weblogic.rmi.internal.ServerRequest.sendOneWayRaw(ServerRequest.java:92)
          at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:112)
          at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:253)
          at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:220)
          at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
          at $Proxy126.create(Unknown Source)
          at examples.wtc.atmi.simpapp.ToupperBean.putMessage(ToupperBean.java:194)
          at examples.wtc.atmi.simpapp.ToupperBean_8roqg7_EOImpl.putMessage(ToupperBean_8roqg7_EOImpl.java:284)
          at examples.wtc.atmi.simpapp.ToupperBean_8roqg7_EOImpl_WLSkel.invoke(Unknown
          Source)
          at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:288)
          at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:257)
          at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          Regards
          Ranga Rao


          Oracle Server 8.1.5 does not provide support for 2PC.
          Full XA support is provided from version 8.1.7.
          Sergi
          "Lawrence" <[email protected]> wrote:
          >
          >Ranga,
          >Please use classes12.zip for this.If you still find problem, please let
          >me know.
          >Thanks
          >Lawrence
          >
          >"Ranga Rao" <[email protected]> wrote:
          >>
          >>
          >>Which version of jdbc thin driver should i use to achieve distributed transaction
          >>with oracle 8.1.5 in weblogic 6.1 sp2
          >>
          >>right now if iam using the driver classes provided in weblogic.jar iam
          >gettig
          >>the
          >>following Exception
          >>
          >>////////////////////////////////////////////////////////////////////////////////////////////
          >>AccountBean.ejbCreate( id = accountId, initial balance = $ 3000.0)
          >>java.sql.SQLException: XA error: XAER_RMERR : A resource manager error
          >has
          >>occured
          >>in the transaction branch start(
          >>) failed on resource 'OracleXAPool' Unexpected error during start for XAResource
          >>'OracleXAPool': null
          >> at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1044)
          >> at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1010)
          >> at weblogic.jdbc.jta.Connection.getXAConn(Connection.java:148)
          >> at weblogic.jdbc.jta.Connection.prepareStatement(Connection.java:226)
          >> at weblogic.jdbc.rmi.internal.ConnectionImpl.prepareStatement(ConnectionImpl.java:135)
          >> at weblogic.jdbc.rmi.SerialConnection.prepareStatement(SerialConnection.java:76)
          >> at examples.ejb.basic.beanManaged.AccountBean.ejbCreate(Unknown
          >>Source)
          >> at examples.ejb.basic.beanManaged.AccountBean_g1748h_Impl.ejbCreate(AccountBean_g1748h_Impl.java:172)
          >> at java.lang.reflect.Method.invoke(Native Method)
          >> at weblogic.ejb20.manager.DBManager.create(DBManager.java:492)
          >> at weblogic.ejb20.manager.DBManager.remoteCreate(DBManager.java:462)
          >> at weblogic.ejb20.internal.EntityEJBHome.create(EntityEJBHome.java:190)
          >> at examples.ejb.basic.beanManaged.AccountBean_g1748h_HomeImpl.create(AccountBean_g1748h_HomeImpl.java:76)
          >> at examples.ejb.basic.beanManaged.AccountBean_g1748h_HomeImpl_WLSkel.invoke(Unknown
          >>Source)
          >> at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:288)
          >> at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
          >> at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:257)
          >> at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:158)
          >> at weblogic.rmi.internal.ServerRequest.sendOneWayRaw(ServerRequest.java:92)
          >> at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:112)
          >> at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:253)
          >> at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:220)
          >> at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
          >> at $Proxy126.create(Unknown Source)
          >> at examples.wtc.atmi.simpapp.ToupperBean.putMessage(ToupperBean.java:194)
          >> at examples.wtc.atmi.simpapp.ToupperBean_8roqg7_EOImpl.putMessage(ToupperBean_8roqg7_EOImpl.java:284)
          >> at examples.wtc.atmi.simpapp.ToupperBean_8roqg7_EOImpl_WLSkel.invoke(Unknown
          >>Source)
          >> at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:288)
          >> at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:257)
          >> at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
          >> at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
          >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          >>/////////////////////////////////////////////////////////////////////////////////
          >>
          >>Regards
          >>Ranga Rao
          >>
          >>
          >

Distributed transactions and 2-phase commit in a SAP Netweaver environment

Hello,
I am a Java architect., I don't know very much the SAP technologies. I tried to found on forums or technical papers if SAP does support distributed transactions and two-phase commit, it's not clear. I found something on SAP WAS but my project is using a SAP PI 7.0 and I cannot find anything on the subject.
My goal is to include a SAP server (via PI 7.0) in a distributed transaction handled by a J2EE ESB (Oracle, ex-BEA Aqualogic) based on XA capabilities.
Does anyone have experience or feedback on this topic ?
Thanks.

Hi,
Do you know this white paper ?
[Distributed Transaction and 2 phase commit|https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/3732d690-0201-0010-a993-b92aab79701f]
Regards,
Olivier

"in-doubt distributed transaction" (WLS 8.1 SP2/Oracle 9.2.0.4)

          I've developed an MDB that reads a message from a queue, performs database updates
          against up to 2 databases, and sends an outgoing JMS message when all is complete.
          The MDB uses container-managed transactions to ensure that all DB updates and
          JMS messages are committed or rolled back together. I have had a lot of problems
          related to transactions failing, becoming "in-doubt" in the database and locking
          database resources indefinitely.
          My environment is configured as follows:
          WebLogic 8.1.2 Server
          Oracle 9.2.0.4 database with RAC
          XA Connection Pool with WebLogic Type 2 Oracle Driver OR Oracle 9.2.0.4
          OCI Driver
          I have read the BEA/HP white paper regarding Weblogic 8.1 with Oracle 9i RAC (http://dev2dev.bea.com/products/wlserver81/whitepapers/wls_bea_hp.jsp)
          and have tried all of the solutions suggested in that paper. The only solution
          that worked consistently without causing the in-doubt transactions was to change
          my connection pools to point directly to a single node of the RAC cluster, not
          to the shared instance. However, even with this configuration, I have seen these
          errors occur when certain database failures occur.
          A side-effect of this problem is that the associated WebLogic connection pools
          begin to "forget" connections. The pool thinks that all of the connections are
          in use (even though I am always calling Statement.close() and Connection.close()),
          and the connection pool cannot be reset manually. The only way to clear the connection
          pool is to bounce WebLogic.
          The only posts I have found related to this error were regarding Oracle 8.1.7
          and WebLogic 6.1. Any help would be greatly appreciated.
          Exceptions:
          <Mar 23, 2004 2:59:36 PM EST> <Error> <EJB> <BEA-010026> <Exception occurred during
          commit of transaction Xid=BEA1-0526A28664707F28EDB9(6412513),Status=Rolled back.
          [Reason=javax.transaction.xa.XAException
          : prepare failed for XAResource 'ProfilingPool' with error XAER_NOTA : The XID
          is not valid],numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=2,seconds
          left=60,XAServerResourceInfo[JMS_my
          JmsStore]=(ServerResourceInfo[JMS_myJmsStore]=(state=rolledback,assigned=myserver),xar=JMS_myJmsStore),XAServerResourceInfo[ProfilingPool]=(ServerResourceInfo[ProfilingPool]=(state=rolledback,ass
          igned=myserver),xar=ProfilingPool),SCInfo[mydomain+myserver]=(state=rolledback),local
          properties=({}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=myserver+10.41.0.61:7001+m
          ydomain+t3+, XAResources={JMS_myJmsStore, JMS_FileStore, ProfilingPool, SearchManagementPool,
          AnnouncementsTxPool},NonXAResources={})],CoordinatorURL=myserver+10.41.0.61:7001+mydomain+t3+):
          javax.tran
          saction.xa.XAException: prepare failed for XAResource 'ProfilingPool' with error
          XAER_NOTA : The XID is not valid
          at weblogic.jdbc.oci.xa.XA.createException(XA.java:386)
          at weblogic.jdbc.oci.xa.XADataSource.internalPrepare(XADataSource.java:905)
          at weblogic.jdbc.oci.xa.XADataSource.prepare(XADataSource.java:885)
          at weblogic.jdbc.jta.DataSource.prepare(DataSource.java:846)
          at weblogic.transaction.internal.XAServerResourceInfo.prepare(XAServerResourceInfo.java:1167)
          at weblogic.transaction.internal.XAServerResourceInfo.prepare(XAServerResourceInfo.java:401)
          at weblogic.transaction.internal.ServerSCInfo$1.execute(ServerSCInfo.java:253)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
          --------------- nested within: ------------------
          weblogic.transaction.RollbackException: Could not prepare resource 'ProfilingPool
          prepare failed for XAResource 'ProfilingPool' with error XAER_NOTA : The XID is
          not valid - with nested exception:
          [javax.transaction.xa.XAException: prepare failed for XAResource 'ProfilingPool'
          with error XAER_NOTA : The XID is not valid]
          at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1644)
          at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:300)
          at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:221)
          at weblogic.ejb20.internal.MDListener.execute(MDListener.java:412)
          at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:316)
          at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:281)
          at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2596)
          at weblogic.jms.client.JMSSession.execute(JMSSession.java:2516)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
          2004-03-23 15:00:45,406 ERROR IS003989 [ExecuteThread: '17' for queue: 'ProfileCompleteListenerBean.ExecuteQueue']
          my.package.search.business.ProfiledHoldingDAO.setProfilingStatus(ProfiledHoldingDAO.java:350
          ) - Failed to update profiling status for holding 10014 [] (-2)
          java.sql.SQLException: ORA-02049: timeout: distributed transaction waiting for
          lock
          at weblogic.db.oci.OciCursor.getCDAException(OciCursor.java:282)
          at weblogic.jdbc.oci.PreparedStatement.executeUpdate(PreparedStatement.java:226)
          at weblogic.jdbc.oci.xa.PreparedStatement.executeUpdate(PreparedStatement.java:81)
          at weblogic.jdbc.wrapper.PreparedStatement.executeUpdate(PreparedStatement.java:94)
          at my.package.search.business.ProfiledHoldingDAO.setProfilingStatus(ProfiledHoldingDAO.java:345)
          at my.package.search.business.ProfilingManager.disseminateAndAcknowledge(ProfilingManager.java:254)
          at my.package.search.business.ProfileCompleteListenerBean.onMessage(ProfileCompleteListenerBean.java:128)
          at weblogic.ejb20.internal.MDListener.execute(MDListener.java:382)
          at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:316)
          at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:281)
          at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2596)
          at weblogic.jms.client.JMSSession.execute(JMSSession.java:2516)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
          2004-03-23 15:01:43,093 ERROR IS003989 [ExecuteThread: '18' for queue: 'HoldingStatusListenerBean.ExecuteQueue']
          my.package.search.business.ProfiledHoldingDAO.getProfilingStatus(ProfiledHoldingDAO.java:265)
          - Failed to retrieve profiling results for holding 10060 [] (-2)
          java.sql.SQLException: ORA-01591: lock held by in-doubt distributed transaction
          189.47.12
          at weblogic.db.oci.OciCursor.getCDAException(OciCursor.java:282)
          at weblogic.jdbc.oci.PreparedStatement.executeQuery(PreparedStatement.java:152)
          at weblogic.jdbc.oci.xa.PreparedStatement.executeQuery(PreparedStatement.java:48)
          at weblogic.jdbc.wrapper.PreparedStatement.executeQuery(PreparedStatement.java:80)
          at my.package.search.business.ProfiledHoldingDAO.getProfilingStatus(ProfiledHoldingDAO.java:256)
          at my.package.search.business.ProfiledHoldingDAO.storeHoldingMetadata(ProfiledHoldingDAO.java:489)
          at my.package.search.business.ProfiledHoldingDAO.storeNewHolding(ProfiledHoldingDAO.java:406)
          at my.package.search.business.ProfilingManager.profileHolding(ProfilingManager.java:128)
          at my.package.search.business.HoldingStatusListenerBean.onMessage(HoldingStatusListenerBean.java:121)
          at weblogic.ejb20.internal.MDListener.execute(MDListener.java:382)
          at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:316)
          at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:281)
          at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2596)
          at weblogic.jms.client.JMSSession.execute(JMSSession.java:2516)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)


Hi. There is a serious bug in the Oracle DBMS (all versions) where in-doubt
          transactions have their data locked in the DBMS by page rather than by row,
          so it will indefinitely prevent access to all data on the page, including
          logically uninvolved data. Oracle understands the problem but currently
          says they will never fix it (it would take too much work). They offer the
          alternative that you configure your table data to ensure that no more than
          one datarow resides on a page.
          Joe
          Matt Smith wrote:
          > I've developed an MDB that reads a message from a queue, performs database updates
          > against up to 2 databases, and sends an outgoing JMS message when all is complete.
          > The MDB uses container-managed transactions to ensure that all DB updates and
          > JMS messages are committed or rolled back together. I have had a lot of problems
          > related to transactions failing, becoming "in-doubt" in the database and locking
          > database resources indefinitely.
          >
          > My environment is configured as follows:
          > WebLogic 8.1.2 Server
          > Oracle 9.2.0.4 database with RAC
          > XA Connection Pool with WebLogic Type 2 Oracle Driver OR Oracle 9.2.0.4
          > OCI Driver
          >
          > I have read the BEA/HP white paper regarding Weblogic 8.1 with Oracle 9i RAC (http://dev2dev.bea.com/products/wlserver81/whitepapers/wls_bea_hp.jsp)
          > and have tried all of the solutions suggested in that paper. The only solution
          > that worked consistently without causing the in-doubt transactions was to change
          > my connection pools to point directly to a single node of the RAC cluster, not
          > to the shared instance. However, even with this configuration, I have seen these
          > errors occur when certain database failures occur.
          >
          > A side-effect of this problem is that the associated WebLogic connection pools
          > begin to "forget" connections. The pool thinks that all of the connections are
          > in use (even though I am always calling Statement.close() and Connection.close()),
          > and the connection pool cannot be reset manually. The only way to clear the connection
          > pool is to bounce WebLogic.
          >
          > The only posts I have found related to this error were regarding Oracle 8.1.7
          > and WebLogic 6.1. Any help would be greatly appreciated.
          >
          > Exceptions:
          > -----------------
          > <Mar 23, 2004 2:59:36 PM EST> <Error> <EJB> <BEA-010026> <Exception occurred during
          > commit of transaction Xid=BEA1-0526A28664707F28EDB9(6412513),Status=Rolled back.
          > [Reason=javax.transaction.xa.XAException
          > : prepare failed for XAResource 'ProfilingPool' with error XAER_NOTA : The XID
          > is not valid],numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=2,seconds
          > left=60,XAServerResourceInfo[JMS_my
          > JmsStore]=(ServerResourceInfo[JMS_myJmsStore]=(state=rolledback,assigned=myserver),xar=JMS_myJmsStore),XAServerResourceInfo[ProfilingPool]=(ServerResourceInfo[ProfilingPool]=(state=rolledback,ass
          > igned=myserver),xar=ProfilingPool),SCInfo[mydomain+myserver]=(state=rolledback),local
          > properties=({}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=myserver+10.41.0.61:7001+m
          > ydomain+t3+, XAResources={JMS_myJmsStore, JMS_FileStore, ProfilingPool, SearchManagementPool,
          > AnnouncementsTxPool},NonXAResources={})],CoordinatorURL=myserver+10.41.0.61:7001+mydomain+t3+):
          > javax.tran
          > saction.xa.XAException: prepare failed for XAResource 'ProfilingPool' with error
          > XAER_NOTA : The XID is not valid
          > at weblogic.jdbc.oci.xa.XA.createException(XA.java:386)
          > at weblogic.jdbc.oci.xa.XADataSource.internalPrepare(XADataSource.java:905)
          > at weblogic.jdbc.oci.xa.XADataSource.prepare(XADataSource.java:885)
          > at weblogic.jdbc.jta.DataSource.prepare(DataSource.java:846)
          > at weblogic.transaction.internal.XAServerResourceInfo.prepare(XAServerResourceInfo.java:1167)
          > at weblogic.transaction.internal.XAServerResourceInfo.prepare(XAServerResourceInfo.java:401)
          > at weblogic.transaction.internal.ServerSCInfo$1.execute(ServerSCInfo.java:253)
          > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
          > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
          > --------------- nested within: ------------------
          > weblogic.transaction.RollbackException: Could not prepare resource 'ProfilingPool
          > prepare failed for XAResource 'ProfilingPool' with error XAER_NOTA : The XID is
          > not valid - with nested exception:
          > [javax.transaction.xa.XAException: prepare failed for XAResource 'ProfilingPool'
          > with error XAER_NOTA : The XID is not valid]
          > at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1644)
          > at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:300)
          > at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:221)
          > at weblogic.ejb20.internal.MDListener.execute(MDListener.java:412)
          > at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:316)
          > at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:281)
          > at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2596)
          > at weblogic.jms.client.JMSSession.execute(JMSSession.java:2516)
          > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
          > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
          > ...
          > 2004-03-23 15:00:45,406 ERROR IS003989 [ExecuteThread: '17' for queue: 'ProfileCompleteListenerBean.ExecuteQueue']
          > my.package.search.business.ProfiledHoldingDAO.setProfilingStatus(ProfiledHoldingDAO.java:350
          > ) - Failed to update profiling status for holding 10014 [] (-2)
          > java.sql.SQLException: ORA-02049: timeout: distributed transaction waiting for
          > lock
          > at weblogic.db.oci.OciCursor.getCDAException(OciCursor.java:282)
          > at weblogic.jdbc.oci.PreparedStatement.executeUpdate(PreparedStatement.java:226)
          > at weblogic.jdbc.oci.xa.PreparedStatement.executeUpdate(PreparedStatement.java:81)
          > at weblogic.jdbc.wrapper.PreparedStatement.executeUpdate(PreparedStatement.java:94)
          > at my.package.search.business.ProfiledHoldingDAO.setProfilingStatus(ProfiledHoldingDAO.java:345)
          > at my.package.search.business.ProfilingManager.disseminateAndAcknowledge(ProfilingManager.java:254)
          > at my.package.search.business.ProfileCompleteListenerBean.onMessage(ProfileCompleteListenerBean.java:128)
          > at weblogic.ejb20.internal.MDListener.execute(MDListener.java:382)
          > at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:316)
          > at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:281)
          > at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2596)
          > at weblogic.jms.client.JMSSession.execute(JMSSession.java:2516)
          > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
          > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
          > ...
          > 2004-03-23 15:01:43,093 ERROR IS003989 [ExecuteThread: '18' for queue: 'HoldingStatusListenerBean.ExecuteQueue']
          > my.package.search.business.ProfiledHoldingDAO.getProfilingStatus(ProfiledHoldingDAO.java:265)
          > - Failed to retrieve profiling results for holding 10060 [] (-2)
          > java.sql.SQLException: ORA-01591: lock held by in-doubt distributed transaction
          > 189.47.12
          > at weblogic.db.oci.OciCursor.getCDAException(OciCursor.java:282)
          > at weblogic.jdbc.oci.PreparedStatement.executeQuery(PreparedStatement.java:152)
          > at weblogic.jdbc.oci.xa.PreparedStatement.executeQuery(PreparedStatement.java:48)
          > at weblogic.jdbc.wrapper.PreparedStatement.executeQuery(PreparedStatement.java:80)
          > at my.package.search.business.ProfiledHoldingDAO.getProfilingStatus(ProfiledHoldingDAO.java:256)
          > at my.package.search.business.ProfiledHoldingDAO.storeHoldingMetadata(ProfiledHoldingDAO.java:489)
          > at my.package.search.business.ProfiledHoldingDAO.storeNewHolding(ProfiledHoldingDAO.java:406)
          > at my.package.search.business.ProfilingManager.profileHolding(ProfilingManager.java:128)
          > at my.package.search.business.HoldingStatusListenerBean.onMessage(HoldingStatusListenerBean.java:121)
          > at weblogic.ejb20.internal.MDListener.execute(MDListener.java:382)
          > at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:316)
          > at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:281)
          > at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2596)
          > at weblogic.jms.client.JMSSession.execute(JMSSession.java:2516)
          > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
          > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
          >
          >

How to implement Distributed Transaction

Hi,
We are using Jsp/Struts/Bc4j application model. JHeadstart 9.0.5.1.
We have the Distributed transaction issue. There are 2 BC4J Application Modules (AM1 and AM2), each with its own DB connection, Entity and View Objects. In a special case, when record is inserted via AM1, there have to be record created in the DB, via AM2.
What is the recommended approach to do that? We can't define AM2 as submodule of AM1, because, when instantiated (in the corresponding doDML method on the entity in AM1), it will try to use the connection of AM1, which is wrong. When (which event), and how to instantiate AM2 (ensure write connection), get corresponding View Object, create the other record, and commit everything in one transaction? Btw, we can not use DB link.
Regards,
Vladimir

Hi Vladimir,
It seems to me that this is a generic BC4J issue, independent of JHeadstart. You could post it at the JDeveloper forum at http://otn.oracle.com/discussionforums/jdev.html.
My suggestion (though I'm not sure it would work) would be to explicitly instantiate AM2 at the time you need it within AM1, with code like this:
String amDef = "test.AM2";
String config = "AM2Local";
ApplicationModule am =
Configuration.createRootApplicationModule(amDef,config);
ViewObject vo = am.findViewObject("TestView");
// Work with your appmodule and view object here
Configuration.releaseRootApplicationModule(am,true);By the way, in JDeveloper 10g you can get this piece of code by typing bc4jclient followed directly by Ctrl+Enter.
Hope this helps,
Sandra Muller
JHeadstart Team
Oracle Consulting

Using Distributed Transaction with oracle 9i and VB

How to I get distributed transaction to work between a COM + object in VB and oracle using MSDAORA.1 driver? I keep getting the following error:
error number:
-2147168229
error description:
Cannot connect to the transaction manager or the transaction manager is unavailable.

Oracle 9i works great with VB.NET. I would recommend you to use Oracle Data Provider .NET (ODP.NET) as a database driver
http://otn.oracle.com/tech/windows/odpnet/content.html
for better performance and get full advantage of Oracle 9i features.
Regards
Jagriti
OTN Team @IDC

ECC-6.0 supports XA(Distributed Transactions)&WS-AT(Web Services u0096 Atomic)

Hi
1- Does SAP ECC-6.0 support XA transactions?
XA Transactions stand for (Distributed Transactions).
2- Does SAP ECC-6.0 Web services allow participation in WS-AT?
WS-AT Stands for is Web Services Atomic Transaction specification.
If so please provide the referral point where I can get the Documentation regarding this.
Any earlier reply will be rewarded.

Hi
1. What is meant by XA ?? Please clarify.. I guess, ECC should support..
2. Yes...
SAP supports ATS... Atomic Transaction specification defines protocols that is recognized by SAP. This failure atomicity property is supported by atomic transactions, which have the following familiar ACID properties.
See useful pointers ->
http://specs.xmlsoap.org/ws/2004/10/wsat/wsat1104.pdf
http://soa.sys-con.com/read/39769.htm
http://searchsoa.techtarget.com/sDefinition/0,,sid26_gci1282196,00.html
http://docs.oasis-open.org/ws-tx/wstx-wsat-1.1-spec-pr-01/wstx-wsat-1.1-spec-pr-01.html
Regards
- Atul

Distributed Transaction Processing Services in Oracle RAC 11.2

Hi,
Do we have to set the DTP parameter to TRUE for workload services that are going to be used for distributed transaction processing?
Something like this ...
srvctl modify service -d crm -s xa_01.service.us.oracle.com -x TRUE
Oracle 11.2 document is not very clear on this requirement. At one stage it says...
"Tightly coupled XA transactions no longer require the special type of singleton services (that is, Oracle Distributed Transaction Processing (DTP) services) to be deployed on Oracle RAC database. XA transactions are transparently supported on Oracle RAC databases with any type of services configuration."
But at the end of the same section...
"An external transaction manager, such as OraMTS, coordinates DTP/XA transactions. However, an internal Oracle transaction manager coordinates distributed SQL transactions. Both DTP/XA and distributed SQL transactions must use the DTP service in Oracle RAC."
So do we have to use DTP services with RAC or not?
Thanks,
-Sanjeev
Edited by: user12219014 on 28 Jan, 2011 8:04 PM

Hi Sanjeev,
I have some critical applications using Tuxedo on 10gR1/R2 RAC databases and there is no doubt to have with this versions.
Starting with 11gR1 it seems the main limitation is over...but there are still limitations ! To be honest I will keep the DTP parameter to true after the migration in 11.2 to avoid any problem. It is still recommended even if not mandatory :
To provide improved application performance with distributed transaction processing in Oracle RAC, you may want to take advantage of DTP services. Using DTP services, you can direct all branches of a distributed transaction to a single instance in the cluster. To load balance across the cluster, it is better to have several groups of smaller application servers with each group directing its transactions to a single service, or set of services, than to have one or two larger application servers.
Also check note 462060.1.
Best regards
Phil
Edited by: Philippe Florent on Jan 30, 2011 10:07 AM -- add documentation precision

OWB9.0.4-- ORA-02049: timeout: distributed transaction waiting for lock

I'm running a simple mapping that copies all columns of data (using a filter on date for just current records) from one table in SQL Server into a staging table on my Oracle DW schema. It's using a dblink with transparent gateway for SQL Server, which works fine from SQL*plus.
The map is in default mode (bulk-failoverto-row) with bulk size and commit frequency = 1000.
The audit details show the first 1000 rows selected on the source, with an error on both the source and target tables:
Target--
ORA-02049: timeout: distributed transaction waiting for lock
Source--
ORA-01002: fetch out of sequence ORA-02063: preceding line from INTERGRATION@JXNSQL01
(INTERGRATION@JXNSQL01 is the dblink name)
Any ideas on how I can clear this up?
Thanks,
Paul

Hi,
After having upgraded to 9.0.4 (from 9.0.3) I'm running into exactly the same problems with some of my mappings. Actually I don't get any rows transferred from the mappings that fail.
Out of 7 mappings, 3 worked just liked before while the 4 others just keep on running until I cancel them and I then see the BUSY/ORA-02049 in the Audit Browser.
When comparing the mappings I see that the 3 that works all use some custom Procedures I have made.
The 4 that doesn't work are all very simple - one of them just loads all the content from a table with two columns in my source to another table with two columns in my target! Two of the other mappings that doesn't work includes some simple CASE-expressions.
Both my source and my target resides in a Oracle 9.2.0.3 database (not the same).
Regards,
Bent Madsen

Distributed Transactions and Linked Servers

I'm somewhat of a novice with SQL Server but I'm learning rapidly from an application I'm developing that uses SQL Server very heavily. In conjunction with the development of this application, I have 3-4 systems set up running SQL Server and I am using those
systems to develop the database that will ultimately support the application. I decided to try to use linked servers because I am moving data back-and-forth among the different servers frequently and I ran into some consequences that I wasn't expecting.
I was doing a simple delete query on one of the servers (Delete from TableName Where ...) and I was expecting, of course, that it would only impact the server I was running it on; however, when the query finished after running for a long time, it was apparent
that SQL Server had automatically escalated that simple delete query into a distributed transaction and applied it to all four of the linked servers I had defined. I was totally surprised by that and it took some time to recover the data that was inadvertently
lost on the other servers.
I want to ensure that this doesn't happen again without me expecting it - I think the right way to prevent this from happening is to run the following stored procedure:
EXEC sp_serveroption 'servername', 'remote proc transaction promotion', 'false';
Can someone please verify that this assumption is correct and will prevent SQL Server from automatically creating distributed transactions impacting multiple servers?
Thanks,
Chuck

Hello,
Based on your description, it seems that when you connect to a SQL Server database and execute a DELETE statement to delete a recode on a table, and then the same recode were delete in the linked server which has the same table.
As pre my understand, the statement executed on one server will not apply to the linked servers unless you specify the logic yourself in the application. For example, you use dynamic query and exec the query synchronously on linked servers.
What's more, did you specify replication between this linked server?
If I have any misunderstanding, please let me know.
Regards,
Fanny Liu
If you have any feedback on our support, please click here.
Fanny Liu
TechNet Community Support

Regarding distributed transaction

Similar Messages

Maybe you are looking for