Jta - distributed transactions

hello,
I'm working on 2 DB 9.2 databases with oc4j version 9.0.2.
I'm trying to implement a distributed transaction using JTA.
I found out that the commit-coordinator must be defined in the application.xml and not in the orion-application.xml, and the data source used for it should be defined in the global data-sources.xml (in the config dir), but now i'm still getting following error when i commit my transaction (on utx.commit(); )
error in execute() : javax.transaction.SystemException: Could not commit: error code 29540- for additional error code check Oracle log file.
What oracle log file ? what code is it giving back ? Is it a ora-... or something else ? Where can i find more info ?
I already start the oc4j container with option
" -Ddatasource.verbose=true -Djdbc.connection.debug=true "
but it doesn't give me more info.
plz help !

Chris,
It seems that there is no Oracle 9i version 9.2.0.4 for
Solaris or NT ?Yes ther is. We are using Oracle 9.2.0.4 on both Solaris 7 and Solaris 9 (on SUN [sparc] computers).
You should be able to get a patch (probably from the MetaLink Web site) that will upgrade your database from 9.2.0.1 to 9.2.04
Good Luck,
Avi.

Similar Messages

EJB 3.0 and JTA (Distributed transactions)

hi, first of all sorry for my english.
then :)
i'm working with JBoss Aplication Server an Oracle DataBase using EJB 3.0
i have no problem before ... but now i want work with multiple database and i wand to manage transactions ... how i understand JTA (Java Transaction Api) is a technology for it.
i think that i need two datasource file for example oracle-xa-ds.xml and postgres-ds.xml
<datasources>
<xa-datasource>
    <jndi-name>XAOracleDS</jndi-name>
    <track-connection-by-tx/>
    <isSameRM-override-value>false</isSameRM-override-value>    <xa-datasource-class>oracle.jdbc.xa.client.OracleXADataSource</xa-datasource-class>
    <xa-datasource-property name="URL">jdbc:oracle:thin:@192.9.200.177:1521:devnbtwo</xa-datasource-property>
    <xa-datasource-property name="User">paata</xa-datasource-property>
    <xa-datasource-property name="Password">1982226</xa-datasource-property>   <exception-sorter-class-name>org.jboss.resource.adapter.jdbc.vendor.OracleExceptionSorter</exception-sorter-class-name>
    <no-tx-separate-pools/>
      <metadata>
         <type-mapping>Oracle9i</type-mapping>
      </metadata>
</xa-datasource>
<mbean code="org.jboss.resource.adapter.jdbc.vendor.OracleXAExceptionFormatter"
         name="jboss.jca:service=OracleXAExceptionFormatter">
    <depends optional-attribute-name="TransactionManagerService">jboss:service=TransactionManager</depends>
</mbean>
</datasources>
<datasources>
<local-tx-datasource>
    <jndi-name>PostgresDS</jndi-name>
   <connection-url>jdbc:postgresql://localhost:5432/Test</connection-url>
    <driver-class>org.postgresql.Driver</driver-class>
    <user-name>postgres</user-name>
    <password>1982226</password>
        <new-connection-sql>select 1</new-connection-sql>
      <metadata>
         <type-mapping>PostgreSQL 7.2</type-mapping>
      </metadata>
</local-tx-datasource>
</datasources>and i dont know what should i do in my persistance.xml file ..... when i was working with single database my persistance.xml file was working
<?xml version="1.0" encoding="UTF-8" ?>
<persistence xmlns="http://java.sun.com/xml/ns/persistence"
     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
     xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd"
     version="1.0">
     <persistence-unit name="Oracle" transaction-type="JTA">
          <jta-data-source>java:/XAOracleDS</jta-data-source>
          <class>com.magti.businesslayer.ejb3entity.Group</class>
          <class>com.magti.businesslayer.ejb3entity.Student</class>
          <properties>
               <property name="hibernate.dialect" value="org.hibernate.dialect.OracleDialect"/>
               <property name="hibernate.connection.driver_class" value="oracle.jdbc.driver.OracleDriver"/>
               <property name="hibernate.connection.url" value="jdbc:oracle:thin:@192.9.200.177:1521:devnbtwo"/>
               <property name="hibernate.connection.username" value="paata"/>
               <property name="hibernate.connection.password" value="1982226"/>
               <property name="hibernate.default_schema" value="PAATA"/>
          </properties>
     </persistence-unit>
</persistence>but then i added anothe unit for second database and i get error
     <persistence-unit name="PostgreSql" transaction-type="JTA">
          <jta-data-source>java:/PostgresDS</jta-data-source>
          <class>com.magti.businesslayer.ejb3entity.Group</class>
          <class>com.magti.businesslayer.ejb3entity.Student</class>
          <properties>
               <property name="hibernate.dialect" value="org.hibernate.dialect.PostgreSQLDialect"/>
               <property name="hibernate.connection.driver_class" value="org.postgresql.Driver"/>
               <property name="hibernate.connection.url" value="jdbc:postgresql://localhost:5432/Test"/>
               <property name="hibernate.connection.username" value="postgres"/>
               <property name="hibernate.connection.password" value="1982226"/>
               <property name="hibernate.default_schema" value="postgres"/>
          </properties>
     </persistence-unit>     i don't know how i resolve it .
i can't find any simple exaplme about distributed transactions on net ...
can anybody help me ....
thanks.

Check this one:
http://www.webagesolutions.com/knowledgebase/javakb/jkb005/index.html

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
          >>
          >>
          >

Database to Middleware distributed transaction control

Hello!
I'm using RMI in a JAVA stored procedure to invoke an external remote object's method (deployed in an application server). Is there any solution to manage the global transaction between database and middleware?
I've the same kind of invocations but from middleware to middleware and in that cases JTA (weblogic transaction manager) manage the transaction.
I've this big challenge in hands. Any idea?
Thanks a lot

Hi Kata,
this won't work as the ALL_TABLES is not a table that exists in your SQl Server - instead it is a "mimicked" table. This means the gateway will check if you have on your SQL Server a table called all_tables and when there's no table it will start an internal mechanism to check out what sort of tables exist in your SQL Server database. So the gateway is starting internally another transaction to get details from the foreign database and DG4ODBC can't participate in distributed transactions at all. Instead of using all_tables you have to use a real SQL Server table like SQ Server sys.objects or sys.tables.
- Klaus

"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)
          >
          >

ORA-02049: timeout: distributed transaction waiting for lock

Hi,
My name is Guneet and I'm working on an application running on BEA Weblogic Server 9.2 running on a Red Hat Linux box using Oracle 10g as the database. My problem is that recently our code started getting the following exception while updating a database table.
java.sql.SQLException: [BEA][Oracle JDBC Driver][Oracle]ORA-02049: timeout: distributed transaction waiting for lock
Application Details
* Using Stateless Session EJB
* Only one Business method in this EJB with transaction attribute set to "required"
* This method executes two select queries & one update query
* We are using JDBC to access the database.
* We have configured a Data Source & are using it to get a database connection.
* Weblogic's Oracle Driver is being used.
More details
* The application has been running well since a month.
* Two days ago,the update query failed with the above error.
* At that time, a single client was accessing the system.
* Once this problem occurs, it starts appearing frequently.
* Eventually a request to get a connection from the Data Source times out & the exception copied at the end is thrown
* At this stage the application gets stuck and all requests trying to get a connection end up with this exception.
* Fortunately, Restarting the Weblogic Server gets us out of this problem and transactions resume normally.
Now my questions are
# Why is this error happening & what does it mean?
# It looks like the second exception (unable to get a connection from ds) is an after effect of the first problem (ORA-02049) once it appears for a couple of times. Can somebody validate this?
# Though I don't understand JTA well but I don't think this application needs distributed transactions so, I'm thinking of modifying the driver type to non-XA oracle driver. Any advise/pointers/comments on this front is welcome !!!!!!!!
Thanks
Guneet Sahai
Exception Trace
Dec 27, 2006 4:47:50 PM | com.gisil.themis.db | SEVERE | Unable to load merchant DEL = 911168900164. Reason - java.sql.SQLException: Unexpected exception while enlisting XAConnection java.sql.SQLException: XA error: XAResource.XAER_RMERR start() failed on resource 'themis-ds': XAER_RMERR : A resource manager error has occured in the transaction branch
javax.transaction.xa.XAException: Unexpected error during start for XAResource 'themis-ds': Transaction timed out after 29 seconds
BEA1-252DE51AC930078CA638
at weblogic.jdbc.wrapper.XA.createException(XA.java:103)
at weblogic.jdbc.jta.DataSource.start(DataSource.java:753)
at weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1182)
at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1115)
at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:274)
at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:497)
at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:429)
at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1408)
at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1332)
at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:440)
at weblogic.jdbc.jta.DataSource.connect(DataSource.java:396)
at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:359)
at com.gisil.themis.db.impl1.DbManagerImpl.isPinValid(DbManagerImpl.java:872)
at com.gisil.themis.ejb.ThemisBean.isPinValid(ThemisBean.java:185)
at com.gisil.themis.ejb.Themis_aqqc4k_EOImpl.isPinValid(Themis_aqqc4k_EOImpl.java:207)
at com.gisil.themis.ejb.Themis_aqqc4k_EOImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:517)
at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:224)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:407)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:403)
at weblogic.rmi.internal.BasicServerRef.access$300(BasicServerRef.java:56)
at weblogic.rmi.internal.BasicServerRef$BasicExecuteRequest.run(BasicServerRef.java:934)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1413)
at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1332)
at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:440)
at weblogic.jdbc.jta.DataSource.connect(DataSource.java:396)
at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:359)
at com.gisil.themis.db.impl1.DbManagerImpl.isPinValid(DbManagerImpl.java:872)
at com.gisil.themis.ejb.ThemisBean.isPinValid(ThemisBean.java:185)
at com.gisil.themis.ejb.Themis_aqqc4k_EOImpl.isPinValid(Themis_aqqc4k_EOImpl.java:207)
at com.gisil.themis.ejb.Themis_aqqc4k_EOImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:517)
at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:224)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:407)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:403)
at weblogic.rmi.internal.BasicServerRef.access$300(BasicServerRef.java:56)
at weblogic.rmi.internal.BasicServerRef$BasicExecuteRequest.run(BasicServerRef.java:934)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)

guneet sahai wrote:
Hi,
My name is Guneet and I'm working on an application running on BEA Weblogic Server 9.2 running on a Red Hat Linux box using Oracle 10g as the database. My problem is that recently our code started getting the following exception while updating a database table.
java.sql.SQLException: [BEA][Oracle JDBC Driver][Oracle]ORA-02049: timeout: distributed transaction waiting for lock
Application Details
* Using Stateless Session EJB
* Only one Business method in this EJB with transaction attribute set to "required"
* This method executes two select queries & one update query
* We are using JDBC to access the database.
* We have configured a Data Source & are using it to get a database connection.
* Weblogic's Oracle Driver is being used.
More details
* The application has been running well since a month.
* Two days ago,the update query failed with the above error.
* At that time, a single client was accessing the system.
* Once this problem occurs, it starts appearing frequently.
* Eventually a request to get a connection from the Data Source times out & the exception copied at the end is thrown
* At this stage the application gets stuck and all requests trying to get a connection end up with this exception.
* Fortunately, Restarting the Weblogic Server gets us out of this problem and transactions resume normally.
Now my questions are
# Why is this error happening & what does it mean?
# It looks like the second exception (unable to get a connection from ds) is an after effect of the first problem (ORA-02049) once it appears for a couple of times. Can somebody validate this?
# Though I don't understand JTA well but I don't think this application needs distributed transactions so, I'm thinking of modifying the driver type to non-XA oracle driver. Any advise/pointers/comments on this front is welcome !!!!!!!!
Thanks
Guneet SahaiHi Guneet. If you want to debug the JTA issue, I suggest opening an official
support case. They will lead you through producing the JTA debug information.
However, I believe you are correct that the transaction you describe is
completely doable with a simple local transaction, so if you were to alter
your pool to use the non-XA driver, it would probably be faster, simpler,
and just work.
Let me know...
Joe
>
Exception Trace
Dec 27, 2006 4:47:50 PM | com.gisil.themis.db | SEVERE | Unable to load merchant DEL = 911168900164. Reason - java.sql.SQLException: Unexpected exception while enlisting XAConnection java.sql.SQLException: XA error: XAResource.XAER_RMERR start() failed on resource 'themis-ds': XAER_RMERR : A resource manager error has occured in the transaction branch
javax.transaction.xa.XAException: Unexpected error during start for XAResource 'themis-ds': Transaction timed out after 29 seconds
BEA1-252DE51AC930078CA638
at weblogic.jdbc.wrapper.XA.createException(XA.java:103)
at weblogic.jdbc.jta.DataSource.start(DataSource.java:753)
at weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1182)
at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1115)
at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:274)
at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:497)
at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:429)
at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1408)
at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1332)
at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:440)
at weblogic.jdbc.jta.DataSource.connect(DataSource.java:396)
at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:359)
at com.gisil.themis.db.impl1.DbManagerImpl.isPinValid(DbManagerImpl.java:872)
at com.gisil.themis.ejb.ThemisBean.isPinValid(ThemisBean.java:185)
at com.gisil.themis.ejb.Themis_aqqc4k_EOImpl.isPinValid(Themis_aqqc4k_EOImpl.java:207)
at com.gisil.themis.ejb.Themis_aqqc4k_EOImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:517)
at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:224)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:407)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:403)
at weblogic.rmi.internal.BasicServerRef.access$300(BasicServerRef.java:56)
at weblogic.rmi.internal.BasicServerRef$BasicExecuteRequest.run(BasicServerRef.java:934)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1413)
at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1332)
at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:440)
at weblogic.jdbc.jta.DataSource.connect(DataSource.java:396)
at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:359)
at com.gisil.themis.db.impl1.DbManagerImpl.isPinValid(DbManagerImpl.java:872)
at com.gisil.themis.ejb.ThemisBean.isPinValid(ThemisBean.java:185)
at com.gisil.themis.ejb.Themis_aqqc4k_EOImpl.isPinValid(Themis_aqqc4k_EOImpl.java:207)
at com.gisil.themis.ejb.Themis_aqqc4k_EOImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:517)
at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:224)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:407)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:403)
at weblogic.rmi.internal.BasicServerRef.access$300(BasicServerRef.java:56)
at weblogic.rmi.internal.BasicServerRef$BasicExecuteRequest.run(BasicServerRef.java:934)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)

Distributed transaction just involving JMS

Hi,
          I have a MDB using a REMOTE DESTINATION to get the messages. The remote
          destination is a Topic using a Connection factory set up as following:
          User Transactions Enabled = true
          XAConnection Factory Enabled = true
          The MDB is set to type-transaction=Container and has a durable
          suscription for the Topic.
          Although, I know I´m using distributed transaction (XAConnection Factory
          Enabled = true) I am not sure if it is correct or not.
          I read that a distributed transaction is when you have 2 resources
          participating in the transaction, but, as you can see I have just JMS
          involved.
          Should I use distributed transaction or not ?
          Any comments will be appreciated!
          Thanks,
          Edith Rivera


ok Thanks for your help !
          Edith
          Peter Holditch wrote:
          > Edith,
          >
          > You should use JTA in the normal way, as you describe.
          >
          > If at commit time there is only 1 participant in the transaction (as
          > seems to ber the case in your instance) then the transaction manager
          > will optimise out the prepare phase of the processing, and you end up
          > with a single phase commit automatically.
          >
          > Regards,
          > Peter.
          >
          > Edith Rivera wrote:
          >
          >> Hi,
          >>
          >> I have a MDB using a REMOTE DESTINATION to get the messages. The
          >> remote destination is a Topic using a Connection factory set up as
          >> following:
          >> User Transactions Enabled = true
          >> XAConnection Factory Enabled = true
          >>
          >> The MDB is set to type-transaction=Container and has a durable
          >> suscription for the Topic.
          >>
          >> Although, I know I´m using distributed transaction (XAConnection
          >> Factory Enabled = true) I am not sure if it is correct or not.
          >> I read that a distributed transaction is when you have 2 resources
          >> participating in the transaction, but, as you can see I have just JMS
          >> involved.
          >>
          >> Should I use distributed transaction or not ?
          >>
          >> Any comments will be appreciated!
          >> Thanks,
          >> Edith Rivera
          >>
          >>
          >

Is there any sample RMI-IIOP application using distributed transactions

Hi,
Based on the links below:
http://e-docs.bea.com/wls/docs61/jta/trxrmi.html#1018506
http://e-docs.bea.com/wls/docs61/jta/gstrx.html#1067532
It appears that is possible to have distributed transactions across RMI-IIOP
clients and RMI-IIOP applications (servers).
I am surprised by the note:
Note: These code fragments do not derive from any of the sample applications
that ship with WebLogic Server. They merely illustrate the use of the
UserTransaction object within an RMI application.
The above note suggests that there is no sample code available.
Is there any sample code that illustrates RMI-IIOP applications (servers)
participating in distributed transactions?
Regards,
Dan Cimpoesu

Transaction examples for IIOP are in the works for the next release.
"Dan Cimpoesu" <[email protected]> wrote:
Hi,
Based on the links below:
http://e-docs.bea.com/wls/docs61/jta/trxrmi.html#1018506
http://e-docs.bea.com/wls/docs61/jta/gstrx.html#1067532
It appears that is possible to have distributed transactions across RMI-IIOP
clients and RMI-IIOP applications (servers).
I am surprised by the note:
Note: These code fragments do not derive from any of the sample applications
that ship with WebLogic Server. They merely illustrate the use of the
UserTransaction object within an RMI application.
The above note suggests that there is no sample code available.
Is there any sample code that illustrates RMI-IIOP applications (servers)
participating in distributed transactions?
Regards,
Dan Cimpoesu

Distributed transactions across RMI-IIOP client to RMI-IIOP server do not work

Hi,
          Based on the links below:
          http://e-docs.bea.com/wls/docs61/jta/trxrmi.html#1018506
          http://e-docs.bea.com/wls/docs61/jta/gstrx.html#1067532
          It appears that is possible to have distributed transactions across RMI-IIOP
          clients and RMI-IIOP applications (servers).
          I followed up the "Transactions Sample RMI Code" section but it appears that
          the transaction context is not propagated from client to server. I am also
          surprised by the note:
          Note: These code fragments do not derive from any of the sample applications
          that ship with WebLogic Server. They merely illustrate the use of the
          UserTransaction object within an RMI application.
          The above note suggests that there is no sample code available.
          Is there anyone who successfully had RMI-IIOP applications (servers)
          participating in distributed transactions?
          Is there any sample code that illustrates RMI-IIOP applications (servers)
          participating in distributed transactions?
          If anyone thinks that this should work I will post my code that does not
          work.
          Regards,
          Dan Cimpoesu


But if you look to the diagram:
http://e-docs.bea.com/wls/docs61/jta/gstrx.html#1040200
it suggests that transactional context is passed from clients to RMI-IIOP
servers.
Am I wrong?
Dan
"Andy Piper" <[email protected]> wrote in message
news:[email protected]..
"Dan Cimpoesu" <[email protected]> writes:
Transactions over IIOP are not supported or implemented in WLS 6.1 or
previous. This is a feature of WLS 7.0. In 7.0 we implement OTS.
andy
Hi,
Based on the links below:
http://e-docs.bea.com/wls/docs61/jta/trxrmi.html#1018506
http://e-docs.bea.com/wls/docs61/jta/gstrx.html#1067532
It appears that is possible to have distributed transactions across
RMI-IIOP
clients and RMI-IIOP applications (servers).
I followed up the "Transactions Sample RMI Code" section but it appearsthat
the transaction context is not propagated from client to server. I amalso
surprised by the note:
Note: These code fragments do not derive from any of the sampleapplications
that ship with WebLogic Server. They merely illustrate the use of the
UserTransaction object within an RMI application.
The above note suggests that there is no sample code available.
Is there anyone who successfully had RMI-IIOP applications (servers)
participating in distributed transactions?
Is there any sample code that illustrates RMI-IIOP applications(servers)
participating in distributed transactions?
If anyone thinks that this should work I will post my code that does not
work.
Regards,
Dan Cimpoesu

Distributed transactions across RMI-IIOP client to server do not work

Hi,
Based on the links below:
http://e-docs.bea.com/wls/docs61/jta/trxrmi.html#1018506
http://e-docs.bea.com/wls/docs61/jta/gstrx.html#1067532
It appears that is possible to have distributed transactions across RMI-IIOP
clients and RMI-IIOP applications (servers).
I followed up the "Transactions Sample RMI Code" section but it appears that
the transaction context is not propagated from client to server. I am also
surprised by the note:
Note: These code fragments do not derive from any of the sample applications
that ship with WebLogic Server. They merely illustrate the use of the
UserTransaction object within an RMI application.
The above note suggests that there is no sample code available.
Is there anyone who successfully had RMI-IIOP applications (servers)
participating in distributed transactions?
Is there any sample code that illustrates RMI-IIOP applications (servers)
participating in distributed transactions?
If anyone thinks that this should work I will post my code that does not
work.
Regards,
Dan Cimpoesu

But if you look to the diagram:
http://e-docs.bea.com/wls/docs61/jta/gstrx.html#1040200
it suggests that transactional context is passed from clients to RMI-IIOP
servers.
Am I wrong?
Dan
"Andy Piper" <[email protected]> wrote in message
news:[email protected]..
"Dan Cimpoesu" <[email protected]> writes:
Transactions over IIOP are not supported or implemented in WLS 6.1 or
previous. This is a feature of WLS 7.0. In 7.0 we implement OTS.
andy
Hi,
Based on the links below:
http://e-docs.bea.com/wls/docs61/jta/trxrmi.html#1018506
http://e-docs.bea.com/wls/docs61/jta/gstrx.html#1067532
It appears that is possible to have distributed transactions across
RMI-IIOP
clients and RMI-IIOP applications (servers).
I followed up the "Transactions Sample RMI Code" section but it appearsthat
the transaction context is not propagated from client to server. I amalso
surprised by the note:
Note: These code fragments do not derive from any of the sampleapplications
that ship with WebLogic Server. They merely illustrate the use of the
UserTransaction object within an RMI application.
The above note suggests that there is no sample code available.
Is there anyone who successfully had RMI-IIOP applications (servers)
participating in distributed transactions?
Is there any sample code that illustrates RMI-IIOP applications(servers)
participating in distributed transactions?
If anyone thinks that this should work I will post my code that does not
work.
Regards,
Dan Cimpoesu

Lock held by in-doubt distributed transaction

          I'm having an intermittent problem in our server where a distributed transaction
          between WebLogic JMS (6.1 sp3) and Oracle (using the 9.1.2 XA driver) doesn't
          complete and subsequent attempts to access the rows in question result in:
          java.sql.SQLException: ORA-01591: lock held by in-doubt distributed transaction
          4.33.52658
          Has anybody else seen anything like this?


          Rao,
          The BEA patch is CR095835_610SP4. Apparently there is a corresponding patch for
          SP3 as well. When configuring the jdbc connection pool set XaSetTransactionTimeout
          = true and
          XaTransactionTimeout = yourTimeoutValueInSeconds. This will instruct the Transaction
          manager to set the timeout value on Oracle's XAResource during the two-phase commit
          process. I believe Oracle refers to the timeout value as SesTm.
          Cheers,
          Tony
          "Rao Boppana" <[email protected]> wrote:
          >
          >We are currently facing the same problem. Could you let us know more
          >details about
          >the patch BEA put out to fix this? Is there a patch #/bug #? We are currently
          >running SP4, Oracle 9.2.3 using 9.2.0.1 drivers. We really cannot set
          >our JTA
          >timeout to less than 1 minute and hence we are left with option2. Any
          >help would
          >be greatly appreciated.
          >
          >
          >"Tony Necakov" <[email protected]> wrote:
          >>
          >>Jane,
          >>Thanks for the reply. After talking to Oracle support, we believe we've
          >>discovered
          >>the cause of the problem. Apparently, setting the JTA transaction timeout
          >>does
          >>not affect the default timeout from Oracle's point of view. Consequently,
          >> XA
          >>transactions exceeding 1 minute (Oracle's default) were being marked
          >>by Oracle
          >>as in-doubt. Subsequent commits or rollback from the transaction manager
          >>were
          >>being ignored. The solution is to either knock the JTA timeout value
          >>to something
          >>below Oracle's default or install a BEA patch which allows the transaction
          >>manager
          >>to set the timeout on the Oracle resource manager.
          >>
          >>"Jane Sampson" <[email protected]> wrote:
          >>>Hi Tony,
          >>>
          >>>Yes, I believe there were some problems with 8.1.7. I believe it requires
          >>>an Oracle patch AND a JDriver patch (if you are using the WebLogic
          >JDriver).
          >>>Open a case with support for details.
          >>>
          >>>Thanks,
          >>>
          >>>Jane
          >>>BEA Support
          >>>
          >>>
          >>>"Tony Necakov" <[email protected]> wrote in message
          >>>news:[email protected]...
          >>>>
          >>>> We're seeing the same intermittent problem with Oracle 8.1.7.2 and
          >>>8.1.7.4. The
          >>>> problem occurs with WLS 6.1 service pack 3 and service pack 4.
          >>>>
          >>>> "Jane Sampson" <[email protected]> wrote:
          >>>> >Hi Tim,
          >>>> >
          >>>> >There is an issue has been reported for Oracle 9.2.0.1 Database/Oracle
          >>>> >9.2.0.1 Thin Driver and exhibits this behavior and is being address
          >>>by
          >>>> >both
          >>>> >BEA and Oracle. I would suggest you open a case with Customer Support
          >>>> >and
          >>>> >mention CR090816. It could be the same problem.
          >>>> >
          >>>> >Thanks,
          >>>> >
          >>>> >Jane
          >>>> >BEA Support
          >>>> >
          >>>> >"Tim Dawson" <[email protected]> wrote in message
          >>>> >news:[email protected]...
          >>>> >>
          >>>> >> I'm having an intermittent problem in our server where a distributed
          >>>> >transaction
          >>>> >> between WebLogic JMS (6.1 sp3) and Oracle (using the 9.1.2 XA
          >driver)
          >>>> >doesn't
          >>>> >> complete and subsequent attempts to access the rows in question
          >>>result
          >>>> >in:
          >>>> >>
          >>>> >> java.sql.SQLException: ORA-01591: lock held by in-doubt distributed
          >>>> >transaction
          >>>> >> 4.33.52658
          >>>> >>
          >>>> >> Has anybody else seen anything like this?
          >>>> >
          >>>> >
          >>>>
          >>>
          >>>
          >>
          >

Ora-01591 Lock held in by In-doubt distributed transaction - help required

In my web application i am getting an error @ a particular page. I am using JTA user transaction to mark the transaction boundaries. On commit i am confronting the error "lock held in by In-Doubt transaction. I queried pending_trans$,dba_2pc_pending and force commit the transaction.Also i purged the transaction using Purge_Lost_db_entity. Still after doing all these i am facing the same problem with a new transaction no.
I did all the below steps:
I did follow the below steps:
SELECT * FROM PENDING_TRANS$
SELECT
LOCAL_TRAN_ID, GLOBAL_TRAN_ID, STATE, MIXED, HOST, COMMIT#
FROM
DBA_2PC_PENDING
WHERE
LOCAL _TRAN_ID = '??.';
SELECT LOCAL_TRAN_ID, IN_OUT, DATABASE, INTERFACE
FROM DBA_2PC_NEIGHBORS;
COMMIT FORCE 'local transactionID', 'SCN';
DBMS_TRANSACTION.PURGE_LOST_DB_ENTRY (local transactionID); OR
DBMS_TRANSACTION.PURGE_MIXED (local transactionID);
SELECT s.inst_id,
s.sid,
s.serial#,
p.spid,
s.username,
s.program
FROM gv$session s
JOIN gv$process p ON p.addr = s.paddr AND p.inst_id = s.inst_id
WHERE s.type != 'BACKGROUND'
and s.program='JDBC Thin Client'
ALTER SYSTEM KILL SESSION '102,10' IMMEDIATE;
Database shutdown and restart doesnt work..
Please anyone help..

tis is the result of the query v$version
Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - Prod
PL/SQL Release 10.2.0.3.0 - Production
"CORE 10.2.0.3.0 Production"
TNS for 32-bit Windows: Version 10.2.0.3.0 - Production
NLSRTL Version 10.2.0.3.0 - Production
I use websphere6.1 and oracle 10.2.0.3. using JTA UserTransaction to define boundaries. I am facing tis issue from last week only before it was working fine. I did the commit force as mentioned before to manually unlock transaction.From then i am getting this error. Could u pls help. I m having pressure from onsite, i dont know what is causing the error in one particular flow. I have included the error logs below.
[7/14/10 19:15:54:328 IST] 00000023 WSRdbXaResour E DSRA0304E: XAException occurred. XAException contents and details are:
The XA Error is : -3
The XA Error message is : A resource manager error has occured in the transaction branch.
The Oracle Error code is : 17410
The Oracle Error message is: Internal XA Error
The cause is : null.
[7/14/10 19:15:54:343 IST] 00000023 WSRdbXaResour E DSRA0302E: XAException occurred. Error code is: XAER_RMERR (-3). Exception is: <null>
[7/14/10 19:15:54:359 IST] 00000023 XATransaction E J2CA0027E: An exception occurred while invoking commit on an XA Resource Adapter from dataSource jdbc/ScorecardDataSource, within transaction ID {XidImpl: formatId(57415344), gtrid_length(36), bqual_length(54), data(00000129d13434870000000100000008f0685880e9e9a1514500185d37d88f31da70140400000129d13434870000000100000008f0685880e9e9a1514500185d37d88f31da701404000000010000000000000000000000000001)}: oracle.jdbc.xa.OracleXAException
[7/14/10 19:15:54:531 IST] 00000023 MCWrapper E J2CA0081E: Method cleanup failed while trying to execute method cleanup on ManagedConnection WSRdbManagedConnectionImpl@3e0a3e0a from resource jdbc/ScorecardDataSource. Caught exception: com.ibm.ws.exception.WsException: DSRA0080E: An exception was received by the Data Store Adapter. See original exception message: No more data to read from socket. with SQL State : null SQL Code : 17410
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:125)
[7/14/10 19:15:54:593 IST] 00000023 MCWrapper E J2CA0081E: Method destroy failed while trying to execute method destroy on ManagedConnection WSRdbManagedConnectionImpl@3e0a3e0a from resource No longer available. Caught exception: java.lang.NullPointerException
[7/14/10 19:16:08:093 IST] 00000023 SystemErr R Caused by: java.sql.SQLException: ORA-01591: lock held by in-doubt distributed transaction 9.34.890
Pls help

Toplink distributed transaction support?

I have a database in SQL Server and one in DB2 on the AS/400 and need to update tables in both places and commit the entire transaction.
Can Toplink handle a distributed transaction?

Yes, provided your J2EE container provides the necessary JTA/JTS support. TopLink can be registered with the transaction controller and thus issue and commit its SQL as part of the JTA callbacks.
http://download-east.oracle.com/docs/cd/A97688_12/toplink.903/b10064/enterpri.htm#1020862
If you are mapping both schemas to an object model using TopLink you may also want to look at TopLink's session broker functionality.
http://download-east.oracle.com/docs/cd/A97688_12/toplink.903/b10064/enterpri.htm#1020687
Doug

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

Jta - distributed transactions

Similar Messages

Maybe you are looking for