TXDataSource Error -- XA error: XAER_RMERR

          Hi,
          I am using Weblogic 6.1 with Oracle 8.1.7. I tried configuring TXDataSource as I
          wanted to use Container Managed Transaction through a Session Bean.
          This is how I configured..
          Connection Pool Settings:
          Name - myXAPool
          URL - jdbc:oracle:thin:@myServer:1521:myDb
          DriverClassname - oracle.jdbc.xa.client.OracleXADataSource
          TXDataSource Settings :
          Name - myXADS
          JNDIName - myXADS
          PoolName - myXAPool
          I get the following error when I try to lookup the datasource. I am not sure where
          the problem is as I have configured Connection Pool and TXDataSource as mentioned
          in the documentation.
          java.sql.SQLException: XA error: XAER_RMERR : A resource manager error has occured
          in the transaction branch start() failed on resource 'myXAPool' Unexpected error
          during start for XAResource 'myXAPool': null
          It would be really great if you can help me out.
          Thanks in Advance,
          Sudhir.
          

          Hi Sudhir,
          see reply on JDBC Newsgroup
          Sergi
          "Sudhir Babu" <[email protected]> wrote:
          >
          >Hi Sergi,
          >
          >Thanks for the response.
          >I downloaded the driver for 8.1.7 from Oracle site and put it in classpath
          >in front
          >of weblogic.jar. I still get the same problem. Is there another location
          >where we
          >can download the Oracle driver with the bug fixed ?
          >
          >Regards,
          >Sudhir.
          >
          >"Sergi Vaz" <[email protected]> wrote:
          >>
          >>Hi Sudhir,
          >>
          >>I think you are using Oracle JDBC drivers 8.1.6. They have a bug, they
          >do
          >>not accept
          >>a foreign XID. Use 8.1.7 or higher to solve this problem (in classpath
          >put
          >>them in
          >>front of weblogic.jar).
          >>
          >>Sergi
          >>
          >>
          >>
          >>"Sudhir Babu" <[email protected]> wrote:
          >>>
          >>>Hi,
          >>>
          >>>I am using Weblogic 6.1 with Oracle 8.1.7. I tried configuring TXDataSource
          >>>as I
          >>>wanted to use Container Managed Transaction through a Session Bean.
          >>>This is how I configured..
          >>>
          >>>Connection Pool Settings:
          >>>-------------------------
          >>>Name - myXAPool
          >>>URL - jdbc:oracle:thin:@myServer:1521:myDb
          >>>DriverClassname - oracle.jdbc.xa.client.OracleXADataSource
          >>>
          >>>TXDataSource Settings :
          >>>-----------------------
          >>>Name - myXADS
          >>>JNDIName - myXADS
          >>>PoolName - myXAPool
          >>>
          >>>I get the following error when I try to lookup the datasource. I am not
          >>>sure where
          >>>the problem is as I have configured Connection Pool and TXDataSource as
          >>>mentioned
          >>>in the documentation.
          >>>
          >>>java.sql.SQLException: XA error: XAER_RMERR : A resource manager error
          >>has
          >>>occured
          >>>in the transaction branch start() failed on resource 'myXAPool' Unexpected
          >>>error
          >>>during start for XAResource 'myXAPool': null
          >>>
          >>>It would be really great if you can help me out.
          >>>
          >>>Thanks in Advance,
          >>>Sudhir.
          >>>
          >>
          >
          

Similar Messages

  • XA error: XAER_RMERR  with wlserver6.1

              This is re-post, reformated for clarity, for an urgent problem
              about BEA XA driver related problem.
              This error develops quickly in our designed simple test with these settings:
              1) wlserver6.1 on Ultra 10 with Solaris 8;
              2) XA datasource on another Ultra 10 with Oracle 8i;
              3) Weblogic XA Oracle Driver;
              4) Simulated 50 clients from Windows 2000 IE;
              5) BMT session bean;
              6) Data base contains a simple table with two colomns, name and password.
              7) The test business logic is to get and return the password string, could not
              be simpler.
              The Processing logic(high level) is as follows:
              A) get UserTransaction, and begin transaction;
              B) loop(30 times):
              1) get connection
              2) create statement
              3) execute statement
              4) close result set
              5) close statement
              6) close connection
              C) commit/rollback the tx accordingly.
              Note that:
              1) the 50 simulated clients will generate repeated hits to stress the server.
              2) We changed to use "thin" driver, giving up the XA capability, and the tests
              run OK.
              However, XA is what we absolutely require of.
              So please help identify this problem. It needed, the complete sample code can
              be made available.
              Thanks.
              Here cometh a exception dump:
              ------------------------------------------------------------ java.sql.SQLException:
              XA error: XAER_RMERR : A resource manager
              error has occured in the transaction branch start() failed on resource 'weblogic.jdbc.jta.DataSource'
              start failed for XAResource 'branchoutPool' with error XAER_RMERR : A resource
              manager error has occured in the transaction branch at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1113)
              at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1079) at
              weblogic.jdbc.jta.Connection.getXAConn(Connection.java:148) at weblogic.jdbc.jta.Connection.createStatement(Connection.java:229)
              at weblogic.jdbc.rmi.internal.ConnectionImpl.createStatement(ConnectionImpl.java:126)
              at weblogic.jdbc.rmi.SerialConnection.createStatement(SerialConnection.java:56)
              at simpleEJB.SimpleEJB.hitdb(SimpleEJB.java:57) at simpleEJB.SimpleEJB_1zpe51_EOImpl.hitdb(SimpleEJB_1zpe51_EOImpl.java:79)
              at simpleEJB.SimpleEJB_1zpe51_EOImpl_WLSkel.invoke(Unknown Source) at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
              at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
              at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
              at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:166) 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:262)
              at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:229)
              at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35) at $Proxy83.hitdb(Unknown
              Source) at simpleUI.SimpleProxy.hitdb(SimpleProxy.java:31) at jsp_servlet.__simple._jspService(__simple.java:95)
              at weblogic.servlet.jsp.JspBase.service(JspBase.java:27) at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
              at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:304)
              at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
              at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2495)
              at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2204)
              at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              

    Yuming,
              Generally, an XAER_RMERR means that tha database's xa routine has
              failed, in this case xa_start from Oracle.
              I am not a DBA, so I am no expert at diagnosing database problems. Is
              there anything logged by Oracle in its system logs/whatever that
              indicates why this might have failed?
              With the C version of Oracle's xa, you can turn on tracing in Oracle, I
              don't know if that is possible in java...
              I hope that might point you in the right direction. If not, have you
              contacted BEA support?
              Regards,
              Peter.
              Got a Question? Ask BEA at http://askbea.bea.com
              The views expressed in this posting are solely those of the author, and BEA
              Systems, Inc. does not endorse any of these views.
              BEA Systems, Inc. is not responsible for the accuracy or completeness of
              the
              information provided
              and assumes no duty to correct, expand upon, delete or update any of the
              information contained in this posting.
              

  • XA error XAER_RMERR with wls6.1 and weblogic XA driver

    This error develops quickly in our designed simple test with these settings:
    1) wlserver6.1 on Ultra 10 with Solaris 8;
    2) XA datasource on another Ultra 10 with Oracle 8i;
    3) Weblogic XA Oracle Driver;
    4) Simulated 50 clients from Windows 2000 IE using Microsoft Web Stress test
    suite;
    5) BMT session bean;
    6) Data base contains a simple table with two colomns, name and password.
    7) The test business logic is to get and return the password string, could
    not be simpler.
    The Processing logic(high level) is as follows:
    A) get UserTransaction, and begin transaction;
    B) loop(30 times):
    1) get connection
    2) create statement
    3) execute statement
    4) close result set
    5) close statement
    6) close connection
    C) commit/rollback the tx accordingly.
    Note that:
    1) the 50 simulated clients will generate repeated hits to stress the
    server.
    2) We changed to use "thin" driver, giving up the XA capability, and the
    tests run OK. However, XA is what we absolutely require of. So please help
    identify this problem. It needed, the complete sample code can be made
    available.
    Thanks.
    Here comes the exception dump:
    java.sql.SQLException: XA error: XAER_RMERR : A resource manager error has
    occured in the transaction branch start() failed on resource
    'weblogic.jdbc.jta.DataSource' start failed for XAResource 'branchoutPool'
    with error XAER_RMERR : A resource manager error has occured in the
    transaction branch at
    weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1113) at
    weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1079) at
    weblogic.jdbc.jta.Connection.getXAConn(Connection.java:148) at
    weblogic.jdbc.jta.Connection.createStatement(Connection.java:229) at
    weblogic.jdbc.rmi.internal.ConnectionImpl.createStatement(ConnectionImpl.jav
    a:126) at
    weblogic.jdbc.rmi.SerialConnection.createStatement(SerialConnection.java:56)
    at simpleEJB.SimpleEJB.hitdb(SimpleEJB.java:57) at
    simpleEJB.SimpleEJB_1zpe51_EOImpl.hitdb(SimpleEJB_1zpe51_EOImpl.java:79) at
    simpleEJB.SimpleEJB_1zpe51_EOImpl_WLSkel.invoke(Unknown Source) at
    weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298) at
    weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java
    :93) at
    weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
    at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:166) 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
    :262) at
    weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java
    :229) at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35) at
    $Proxy83.hitdb(Unknown Source) at
    simpleUI.SimpleProxy.hitdb(SimpleProxy.java:31) at
    jsp_servlet.__simple._jspService(__simple.java:95) at
    weblogic.servlet.jsp.JspBase.service(JspBase.java:27) at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
    :265) at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
    :304) at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
    :200) at
    weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletCo
    ntext.java:2495) at
    weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java
    :2204) at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139) at
    weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)

    hi!
    I´m facing the same problem with a similiar configuration.
    Pool is large enough for an elephant! (:>))
    Any other hints?
    regards,
    Pesca
    "Richard Wallace" <[email protected]> escreveu na mensagem
    news:[email protected]...
    >
    Hi,
    What connection pool settings do you have? I assume you have enoughconnections
    for this test?
    Regards,
    Richard Wallace
    Senior Developer Relations Engineer
    BEA Support.
    "Yuming Liu" <[email protected]> wrote:
    This error develops quickly in our designed simple test with these
    settings:
    >>
    1) wlserver6.1 on Ultra 10 with Solaris 8;
    2) XA datasource on another Ultra 10 with Oracle 8i;
    3) Weblogic XA Oracle Driver;
    4) Simulated 50 clients from Windows 2000 IE using Microsoft Web Stress
    test
    suite;
    5) BMT session bean;
    6) Data base contains a simple table with two colomns, name and password.
    7) The test business logic is to get and return the password string,
    could
    not be simpler.
    The Processing logic(high level) is as follows:
    A) get UserTransaction, and begin transaction;
    B) loop(30 times):
    1) get connection
    2) create statement
    3) execute statement
    4) close result set
    5) close statement
    6) close connection
    C) commit/rollback the tx accordingly.
    Note that:
    1) the 50 simulated clients will generate repeated hits to stress the
    server.
    2) We changed to use "thin" driver, giving up the XA capability, and
    the
    tests run OK. However, XA is what we absolutely require of. So please
    help
    identify this problem. It needed, the complete sample code can be made
    available.
    Thanks.
    Here comes the exception dump:
    java.sql.SQLException: XA error: XAER_RMERR : A resource manager error
    has
    occured in the transaction branch start() failed on resource
    'weblogic.jdbc.jta.DataSource' start failed for XAResource'branchoutPool'
    with error XAER_RMERR : A resource manager error has occured in the
    transaction branch at
    weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1113) at
    weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1079)
    at
    weblogic.jdbc.jta.Connection.getXAConn(Connection.java:148) at
    weblogic.jdbc.jta.Connection.createStatement(Connection.java:229) atweblogic.jdbc.rmi.internal.ConnectionImpl.createStatement(ConnectionImpl.jav
    a:126) atweblogic.jdbc.rmi.SerialConnection.createStatement(SerialConnection.java:56)
    at simpleEJB.SimpleEJB.hitdb(SimpleEJB.java:57) at
    simpleEJB.SimpleEJB_1zpe51_EOImpl.hitdb(SimpleEJB_1zpe51_EOImpl.java:79)
    at
    simpleEJB.SimpleEJB_1zpe51_EOImpl_WLSkel.invoke(Unknown Source) at
    weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
    atweblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java
    :93) atweblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
    at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:166)
    at
    weblogic.rmi.internal.ServerRequest.sendOneWayRaw(ServerRequest.java:92)
    at
    weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:112)
    atweblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java
    :262) atweblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java
    :229) at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35) at
    $Proxy83.hitdb(Unknown Source) at
    simpleUI.SimpleProxy.hitdb(SimpleProxy.java:31) at
    jsp_servlet.__simple._jspService(__simple.java:95) at
    weblogic.servlet.jsp.JspBase.service(JspBase.java:27) atweblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
    :265) atweblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
    :304) atweblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
    :200) atweblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletCo
    ntext.java:2495) atweblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java
    :2204) at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at
    weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)

  • XA error: XAER_RMERR : A resource manager error

              When attempting Oracle's XA driver, the exception below occurs when deploying EJB's.
              All EJBs have trans-attr set to Required or Mandatory. The EJB's fail to deploy
              on WLS 8.1
              JDBC Driver used: oracle.jdbc.xa.client.OracleXADataSource
              DataSource is set to support XA.
              Set up followed as described in edocs.bea.com/wls/docs81/jta/thirdpartytx.html
              Any ideas?
              Exception:weblogic.management.ApplicationException: activate failed for iDTV-ejb.jar
              Module: iDTV-ejb.jar Error: Exception activating module: EJBModule(iDTV-ejb.jar,status=PREPARED)
              Unable to deploy EJB: HouseholdMemberE from iDTV-ejb.jar: XA error: XAER_RMERR
              : A resource manager error has occured in the transaction branch start() failed
              on resource 'iDTV_prod_CP': XAER_RMERR : A resource manager error has occured
              in the transaction branch oracle.jdbc.xa.OracleXAException at oracle.jdbc.xa.OracleXAResource.checkError(OracleXAResource.java:1159)
              at oracle.jdbc.xa.client.OracleXAResource.start(OracleXAResource.java:311) at
              weblogic.jdbc.wrapper.VendorXAResource.start(VendorXAResource.java:50) at weblogic.jdbc.jta.DataSource.start(DataSource.java:604)
              at weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1069)
              at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1001)
              at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:203)
              at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:419)
              at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1230) at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1193)
              at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:371) at weblogic.jdbc.jta.DataSource.connect(DataSource.java:329)
              at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:298)
              at weblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.getConnection(RDBMSPersistenceManager.java:1841)
              at weblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.verifyDatabaseType(RDBMSPersistenceManager.java:2025)
              at weblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.setup(RDBMSPersistenceManager.java:195)
              at weblogic.ejb20.manager.BaseEntityManager.setupPM(BaseEntityManager.java:217)
              at weblogic.ejb20.manager.BaseEntityManager.setup(BaseEntityManager.java:184)
              at weblogic.ejb20.manager.DBManager.setup(DBManager.java:164) at weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.activate(ClientDrivenBeanInfoImpl.java:1004)
              at weblogic.ejb20.deployer.EJBDeployer.activate(EJBDeployer.java:1322) at weblogic.ejb20.deployer.EJBModule.activate(EJBModule.java:610)
              at weblogic.j2ee.J2EEApplicationContainer.activateModule(J2EEApplicationContainer.java:3012)
              at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2076)
              at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2057)
              at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.activateContainer(SlaveDeployer.java:2624)
              at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.doCommit(SlaveDeployer.java:2547)
              at weblogic.management.deploy.slave.SlaveDeployer$Task.commit(SlaveDeployer.java:2349)
              at weblogic.management.deploy.slave.SlaveDeployer$Task.checkAutoCommit(SlaveDeployer.java:2431)
              at weblogic.management.deploy.slave.SlaveDeployer$Task.prepare(SlaveDeployer.java:2343)
              at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2511)
              at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:833)
              at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:542)
              at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:500)
              at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
              at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
              

              Refer to
              http://support.bea.com/application?namespace=askbea&origin=ask_bea_answer.jsp&event=link.view_answer_page_clfydoc&answerpage=solution&page=wls%2FS-20733.htm
              "Ignaz Wanders" <[email protected]> wrote:
              >
              >When attempting Oracle's XA driver, the exception below occurs when deploying
              >EJB's.
              >All EJBs have trans-attr set to Required or Mandatory. The EJB's fail
              >to deploy
              >on WLS 8.1
              >
              >JDBC Driver used: oracle.jdbc.xa.client.OracleXADataSource
              >
              >DataSource is set to support XA.
              >
              >Set up followed as described in edocs.bea.com/wls/docs81/jta/thirdpartytx.html
              >
              >Any ideas?
              >
              >Exception:weblogic.management.ApplicationException: activate failed for
              >iDTV-ejb.jar
              >Module: iDTV-ejb.jar Error: Exception activating module: EJBModule(iDTV-ejb.jar,status=PREPARED)
              >Unable to deploy EJB: HouseholdMemberE from iDTV-ejb.jar: XA error: XAER_RMERR
              >: A resource manager error has occured in the transaction branch start()
              >failed
              >on resource 'iDTV_prod_CP': XAER_RMERR : A resource manager error has
              >occured
              >in the transaction branch oracle.jdbc.xa.OracleXAException at oracle.jdbc.xa.OracleXAResource.checkError(OracleXAResource.java:1159)
              >at oracle.jdbc.xa.client.OracleXAResource.start(OracleXAResource.java:311)
              >at
              >weblogic.jdbc.wrapper.VendorXAResource.start(VendorXAResource.java:50)
              >at weblogic.jdbc.jta.DataSource.start(DataSource.java:604)
              >at weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1069)
              >at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1001)
              >at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:203)
              >at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:419)
              >at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1230) at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1193)
              >at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:371) at
              >weblogic.jdbc.jta.DataSource.connect(DataSource.java:329)
              >at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:298)
              >at weblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.getConnection(RDBMSPersistenceManager.java:1841)
              >at weblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.verifyDatabaseType(RDBMSPersistenceManager.java:2025)
              >at weblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.setup(RDBMSPersistenceManager.java:195)
              >at weblogic.ejb20.manager.BaseEntityManager.setupPM(BaseEntityManager.java:217)
              >at weblogic.ejb20.manager.BaseEntityManager.setup(BaseEntityManager.java:184)
              >at weblogic.ejb20.manager.DBManager.setup(DBManager.java:164) at weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.activate(ClientDrivenBeanInfoImpl.java:1004)
              >at weblogic.ejb20.deployer.EJBDeployer.activate(EJBDeployer.java:1322)
              >at weblogic.ejb20.deployer.EJBModule.activate(EJBModule.java:610)
              >at weblogic.j2ee.J2EEApplicationContainer.activateModule(J2EEApplicationContainer.java:3012)
              >at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2076)
              >at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2057)
              >at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.activateContainer(SlaveDeployer.java:2624)
              >at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.doCommit(SlaveDeployer.java:2547)
              >at weblogic.management.deploy.slave.SlaveDeployer$Task.commit(SlaveDeployer.java:2349)
              >at weblogic.management.deploy.slave.SlaveDeployer$Task.checkAutoCommit(SlaveDeployer.java:2431)
              >at weblogic.management.deploy.slave.SlaveDeployer$Task.prepare(SlaveDeployer.java:2343)
              >at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2511)
              >at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:833)
              >at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:542)
              >at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:500)
              >at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
              >at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
              

  • XA error: XAER_RMERR on getConnection()

    I am using WLS 6.1 SP2 and Oracle 8.0.6, Type 4 Driver. I have a connection pool
    that works fine from a javabean, servlet, jsp, etc.
    I am trying to create a BMP EJB, and the call to getConnection returns the following
    error. JNDI seems to resolve the DataSource name okay, but I get back a null connection
    handle. I am not sure if I have a problem with my deployment descriptors or a
    jdbc problem.
    Dec 30, 2002 09:26:53 PersonEJB() - Person.ejbCreate called.
    Dec 30, 2002 09:26:53 create() Got DataSource from JNDI
    Dec 30, 2002 09:26:53 create() Oracle Error: java.sql.SQLException: XA error:
    XAER_RMERR : A resource manager error has occured in the transaction branch start()
    failed on resource 'Thin_Pool' Unexpected error during start for XAResource 'Thin_Pool':
    null
    Any suggestions appreciated.
    Thanks.
    Jeff

    I am using WLS 6.1 SP2 and Oracle 8.0.6, Type 4 Driver. I have a connection pool
    that works fine from a javabean, servlet, jsp, etc.
    I am trying to create a BMP EJB, and the call to getConnection returns the following
    error. JNDI seems to resolve the DataSource name okay, but I get back a null connection
    handle. I am not sure if I have a problem with my deployment descriptors or a
    jdbc problem.
    Dec 30, 2002 09:26:53 PersonEJB() - Person.ejbCreate called.
    Dec 30, 2002 09:26:53 create() Got DataSource from JNDI
    Dec 30, 2002 09:26:53 create() Oracle Error: java.sql.SQLException: XA error:
    XAER_RMERR : A resource manager error has occured in the transaction branch start()
    failed on resource 'Thin_Pool' Unexpected error during start for XAResource 'Thin_Pool':
    null
    Any suggestions appreciated.
    Thanks.
    Jeff

  • TxDataSource Error

    Hi, When I start up my managed server on WLS 7.0 SP7, I get this message pertaining to a TxDataSource.
    The details of the JDBC conn pool, CPODSSYS are:
    URL: jdbc:weblogic:mssqlserver4:[email protected]:1433
    Driver: weblogic.jdbc.mssqlserver4.Driver
    The details of      DSODSSYS datasource are:
    JNDI name: dev_ods
    Pool name: CPODSSYS
    Error message:
    ####<Mar 29, 2006 1:04:05 AM CST> <Error> <SLFC Project> <SLFCWebAppSys> <managed1> <Main Thread> <kernel identity> <> <000000> <CodeValueLoad::init() -> Caught unhandled Exception : Error accessing jdbc driver: driverURL = jdbc:weblogic:pool:CPODSSYS, props = {enableTwoPhaseCommit=false, jdbcTxDataSource=true, connectionPoolID=CPODSSYS, dataSourceName=DSODSSYS}.
    Nested Exception: java.sql.SQLException: Pool connect failed: weblogic.common.ResourceException: Access not allowed
    at weblogic.jdbc.pool.Driver.connect(Driver.java:211)
    at weblogic.jdbc.jts.Driver.getNonTxConnection(Driver.java:376)
    at weblogic.jdbc.jts.Driver.connect(Driver.java:130)
    at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:329)
    at com.slfc.servlets.CodeValueLoad.init(CodeValueLoad.java:75)
    at weblogic.servlet.internal.ServletStubImpl$ServletInitAction.run(ServletStubImpl.java:1121)
    at weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:690)
    at weblogic.servlet.internal.ServletStubImpl.createServlet(ServletStubImpl.java:945)
    at weblogic.servlet.internal.ServletStubImpl.createInstances(ServletStubImpl.java:879)
    at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:819)
    at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:2880)
    at weblogic.servlet.internal.WebAppServletContext.preloadServlets(WebAppServletContext.java:2837)
    Pls suggest and advise.
    Thanx
    Nitin

    Nitin Kumar wrote:
    Hi, When I start up my managed server on WLS 7.0 SP7, I get this message pertaining to a TxDataSource.
    The details of the JDBC conn pool, CPODSSYS are:
    URL: jdbc:weblogic:mssqlserver4:[email protected]:1433
    Driver: weblogic.jdbc.mssqlserver4.Driver
    The details of      DSODSSYS datasource are:
    JNDI name: dev_ods
    Pool name: CPODSSYS
    Error message:
    ####<Mar 29, 2006 1:04:05 AM CST> <Error> <SLFC Project> <SLFCWebAppSys> <managed1> <Main Thread> <kernel identity> <> <000000> <CodeValueLoad::init() -> Caught unhandled Exception : Error accessing jdbc driver: driverURL = jdbc:weblogic:pool:CPODSSYS, props = {enableTwoPhaseCommit=false, jdbcTxDataSource=true, connectionPoolID=CPODSSYS, dataSourceName=DSODSSYS}.
    Nested Exception: java.sql.SQLException: Pool connect failed: weblogic.common.ResourceException: Access not allowed
    at weblogic.jdbc.pool.Driver.connect(Driver.java:211)
    at weblogic.jdbc.jts.Driver.getNonTxConnection(Driver.java:376)
    at weblogic.jdbc.jts.Driver.connect(Driver.java:130)
    at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:329)
    at com.slfc.servlets.CodeValueLoad.init(CodeValueLoad.java:75)Hi. The exception mean that the current WebLogic user does not have WebLogic
    permissions to use the pool. This mean you have to configure weblogic to allow
    such access, but it may be that your code in CodeValueLoad, is trying to pass
    a user and password in a getConnection() call. This is unneeded and superfluous
    because the pool already has connections with it's user and password. Just
    call getConnection(). We implement our DataSource.getConnection(user, password)
    to check the weblogic user/password as a valid configured weblogic user,
    instead of using the current weblogic user credentials.
    Joe
    at weblogic.servlet.internal.ServletStubImpl$ServletInitAction.run(ServletStubImpl.java:1121)
    at weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:690)
    at weblogic.servlet.internal.ServletStubImpl.createServlet(ServletStubImpl.java:945)
    at weblogic.servlet.internal.ServletStubImpl.createInstances(ServletStubImpl.java:879)
    at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:819)
    at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:2880)
    at weblogic.servlet.internal.WebAppServletContext.preloadServlets(WebAppServletContext.java:2837)
    Pls suggest and advise.
    Thanx
    Nitin

  • Error while using TXDataSource with Weblogic 6.1 & Oracle 8.1.6

    Hi,
    I am using Weblogic 6.1 and Oracle 8.1.6.
    I have configured JDBC XA Connection Pool with Oracle thin driver. These are my settings...
    Connection Pool:
    Name - myXAPool
    URL - jdbc:oracle:thin:@myServer:1521:myDb
    DriverClassname - oracle.jdbc.xa.client.OracleXADataSource
    TXDataSource:
    Name - myXADS
    JNDIName - myXADS
    PoolName - myXAPool
    I get the following error when I try to lookup the datasource. I am not sure where the problem is as I have configured Connection Pool and TXDataSource as mentioned in the documentation.
    java.sql.SQLException: XA error: XAER_RMERR : A resource manager error has occured in the transaction branch start() failed on resource 'myXAPool' Unexpected error during start for XAResource 'myXAPool': null
    It would be really great if you can help me out.
    Thanks in Advance,
    Sudhir.

    Hi Sudhir,
    If you do not know if upgrade or not, have a look here :
    http://e-docs.bea.com/wls/docs61/notes/bugfixes2.html
    Note that at the end of June SP3 will be released...
    Sergi
    "Sudhir Babu" <[email protected]> wrote:
    >
    Hi Sergi,
    Thanks a lot for the class file, I figured out what the problem was. Actually
    the
    database version I was working with was 8.0.6.0. The Oracle driver doesn't
    work with
    this but the JDriver worked. This is the output of running CheckDriver..
    DatabaseProductName : Oracle
    DatabaseProductVersion : Oracle8 Enterprise Edition Release 8.0.6.0.0 -
    Production
    With the Partitioning and Objects options
    PL/SQL Release 8.0.6.0.0 - Production
    DriverName : Oracle JDBC driver
    DriverVersion : 8.1.7.1.0
    Then I tried on using the Oracle Driver on another instance which has the
    version
    8.1.7.1.0 and it worked. The JDriver and Oracle driver both work with this
    database.
    The output of CheckDriver for this Oracle instance is..
    DatabaseProductName : Oracle
    DatabaseProductVersion : Oracle8i Enterprise Edition Release 8.1.7.1.0 -
    Production
    With the Partitioning option
    JServer Release 8.1.7.1.0 - Production
    DriverName : Oracle JDBC driver
    DriverVersion : 8.1.7.0.0
    By the way I am working on WLS 6.1 SP1. What is the advantage of SP2 ? Should
    I upgrade
    Thanks once again,
    Sudhir.
    "Sergi Vaz" <[email protected]> wrote:
    Hi Sudhir ,
    JDriver works well, you can work with it.
    Just for curiosity, can you run the class I attached using the "exact"classpath
    of your WL instance (with Oracle drivers in front of weblogic.jar) ? What
    is the
    output ?
    On which platform are you running your WLSP2 ?
    Thanks
    Sergi
    "Sudhir Babu" <[email protected]> wrote:
    Hi Sergi,
    I just checked the things you mentioned. The connection pool starts correctly
    without
    any errors. I also made sure SELECT previlege was granted to DBA_PENDING_TRANSACTIONS.
    I do have the JAVA_XA package installed and it has EXECUTE permission
    to
    PUBLIC.
    I actually tried using the Weblogic JDriver (weblogic.jdbc.oci.xa.XADataSource)
    and
    it works perfect without any issue. The only consideration is that itis
    a Type 2
    Driver and needs to have the Oracle Client installed. But right now Ido
    have it
    installed on the same machine.
    Do you know any known issues with Weblogic JDriver. Do you think it'sa
    good idea
    to go with it ?
    Thanks,
    Sudhir.
    "Sergi Vaz" <[email protected]> wrote:
    Hi Sudhir,
    does your connection pool start correctly ?
    Check the setup of your Oracle server too:
    1) grant select on DBA_PENDING_TRANSACTIONS table to PUBLIC
    2) package JAVA_XA installed (with grant execute to PUBLIC)
    Sergi
    "Sudhir Babu" <[email protected]> wrote:
    Hi Sergi,
    Thanks for the response. I downloaded the driver for 8.1.7 from Oraclesite
    and put
    it in classpath in front of weblogic.jar. I still get the same problem.
    Is there
    another location where we can download the Oracle driver with the bug
    fixed
    Regards, Sudhir.
    "Sergi Vaz" <[email protected]> wrote:
    Hi Sudhir,
    I think you are using Oracle JDBC drivers 8.1.6.
    They have a bug, they do not accept a foreign XID.
    Use 8.1.7 or higher to solve this problem.
    Sergi
    Sudhir Babu <[email protected]> wrote:
    Hi,
    I am using Weblogic 6.1 and Oracle 8.1.6.
    I have configured JDBC XA Connection Pool with Oracle thin driver.
    These
    are my settings...
    Connection Pool:
    Name - myXAPool
    URL - jdbc:oracle:thin:@myServer:1521:myDb
    DriverClassname - oracle.jdbc.xa.client.OracleXADataSource
    TXDataSource:
    Name - myXADS
    JNDIName - myXADS
    PoolName - myXAPool
    I get the following error when I try to lookup the datasource. I amnot
    sure where the problem is as I have configured Connection Pool and
    TXDataSource
    as mentioned in the documentation.
    java.sql.SQLException: XA error: XAER_RMERR : A resource manager errorhas
    occured in the transaction branch start() failed on resource 'myXAPool'
    Unexpected error during start for XAResource 'myXAPool': null
    It would be really great if you can help me out.
    Thanks in Advance,
    Sudhir.

  • Help!.... XA error: using Weblogic 6.1 and Oracle 8.1.6

              Hi,
              I am using Weblogic 6.1 with Oracle 8.1.7. I configured a TXDataSource as I wanted
              to use Container Managed Transaction through a Session Bean.
              Connection Pool Settings: -------------------------
              Name - myXAPool URL - jdbc:oracle:thin:@myServer:1521:myDb DriverClassname - oracle.jdbc.xa.client.OracleXADataSource
              TXDataSource Settings : -----------------------
              Name - myXADS
              JNDIName - myXADS
              PoolName - myXAPool
              Everything works fine but once in a while I get the following exception:
              java.sql.SQLException: XA error: XAER_RMERR : A resource manager error has occured
              in the transaction branch start() failed on resource 'myXAPool' Unexpected error
              during start for XAResource 'myXAPool': null
              The connection pool size is 30 and the number connections high reached was 5,
              which means there are enough connections in the pool available at all time.
              It would be really great if you can help me out.
              Thanks in Advance, Sudhir.
              

    Hi Slava,
    Sorry about that Oracle instance I am using is 8.1.7.
    For the XA Driver I am using the one that comes with Weblogic in weblogic.jar.
    And my Weblogic version 6.1 Sp3.
    Thanks,
    Sudhir.
    "Slava Imeshev" <[email protected]> wrote:
    Hi Sudhir,
    Are you using an instance of 8.1.6 or 8.1.7? In the message header you
    say
    8.1.6.
    Regards,
    Slava Imeshev
    "Sudhir Babu" <[email protected]> wrote in message
    news:[email protected]..
    Hi,
    I am using Weblogic 6.1 with Oracle 8.1.7. I configured a TXDataSourceas
    I wanted
    to use Container Managed Transaction through a Session Bean.
    Connection Pool Settings: -------------------------
    Name - myXAPool URL - jdbc:oracle:thin:@myServer:1521:myDb
    DriverClassname - oracle.jdbc.xa.client.OracleXADataSource
    TXDataSource Settings : -----------------------
    Name - myXADS
    JNDIName - myXADS
    PoolName - myXAPool
    Everything works fine but once in a while I get the following exception:
    java.sql.SQLException: XA error: XAER_RMERR : A resource manager errorhas
    occured
    in the transaction branch start() failed on resource 'myXAPool' Unexpectederror
    during start for XAResource 'myXAPool': null
    The connection pool size is 30 and the number connections high reachedwas
    5,
    which means there are enough connections in the pool available at alltime.
    It would be really great if you can help me out.
    Thanks in Advance, Sudhir.

  • XA error: using Weblogic 6.1 and Oracle 8.1.6

    Hi,
    I am using Weblogic 6.1 with Oracle 8.1.7. I configured a TXDataSource as I wanted
    to use Container Managed Transaction through a Session Bean.
    Connection Pool Settings: -------------------------
    Name - myXAPool URL - jdbc:oracle:thin:@myServer:1521:myDb
    DriverClassname - oracle.jdbc.xa.client.OracleXADataSource
    TXDataSource Settings : -----------------------
    Name - myXADS
    JNDIName - myXADS
    PoolName - myXAPool
    Everything works fine but once in a while I get the following exception:
    java.sql.SQLException: XA error: XAER_RMERR : A resource manager error has occured
    in the transaction branch start() failed on resource 'myXAPool' Unexpected error
    during start for XAResource 'myXAPool': null
    The connection pool size is 30 and the number connections high reached was 5,
    which means there are enough connections in the pool available at all time.
    It would be really great if you can help me out.
    Thanks in Advance, Sudhir.

    Hi Slava,
    Sorry about that Oracle instance I am using is 8.1.7.
    For the XA Driver I am using the one that comes with Weblogic in weblogic.jar.
    And my Weblogic version 6.1 Sp3.
    Thanks,
    Sudhir.
    "Slava Imeshev" <[email protected]> wrote:
    Hi Sudhir,
    Are you using an instance of 8.1.6 or 8.1.7? In the message header you
    say
    8.1.6.
    Regards,
    Slava Imeshev
    "Sudhir Babu" <[email protected]> wrote in message
    news:[email protected]..
    Hi,
    I am using Weblogic 6.1 with Oracle 8.1.7. I configured a TXDataSourceas
    I wanted
    to use Container Managed Transaction through a Session Bean.
    Connection Pool Settings: -------------------------
    Name - myXAPool URL - jdbc:oracle:thin:@myServer:1521:myDb
    DriverClassname - oracle.jdbc.xa.client.OracleXADataSource
    TXDataSource Settings : -----------------------
    Name - myXADS
    JNDIName - myXADS
    PoolName - myXAPool
    Everything works fine but once in a while I get the following exception:
    java.sql.SQLException: XA error: XAER_RMERR : A resource manager errorhas
    occured
    in the transaction branch start() failed on resource 'myXAPool' Unexpectederror
    during start for XAResource 'myXAPool': null
    The connection pool size is 30 and the number connections high reachedwas
    5,
    which means there are enough connections in the pool available at alltime.
    It would be really great if you can help me out.
    Thanks in Advance, Sudhir.

  • Petstore 1.3 with Oracle 8.1.7 on Solaris 9 - deployment error

    Hello,
    I'm trying to get Petstore 1.3 shipped with WebLogic Server 7.0 to work with Oracle
    8.1.7 on Solaris 9 with a third-party (Oracle) jdbc driver (classes12). I did
    the following:
    1) created a new connection pool with the correct Oracle database URL and driver
    class name (oracle.jdbc.driver.OracleDriver), also user/password properties for
    the Oracle db, and the WL server selected in targets;
    2) created a database schema for Oracle based on the data in Pointbase and the
    weblogic-cmp-rdbms-jar file as well as petstore_catalog_utf8.sql;
    3) created a new tx datasource pointing to the Oracle conn pool;
    4) modified the catalog component's ejb-jar.xml file's env-entry to contain CatalogOracleDAOImpl;
    5) put weblogic.jar in the classpath;
    6) used Java's dbping utility to check connection to the database via the Oracle
    driver (works fine--no network adapter error or anything related).
    I then rebuilt the ear files (build is successful), but when deploying get the
    following error:
    "Cannot deploy EJB AccountEJB from customerEjb.jar. Cannot find datasource for
    JNDI datasource-petstorePool" and says to make sure the JNDI name and deployment
    descriptors are correct (I checked the customer component's deployment descriptors
    against the tx datasources' JNDI and they match).
    What step(s) am I missing? Any suggestions on what else I need to modify would
    be very much appreciated.
    Thanks,
    Beverly Claire

    Beverly:
    If you have 8.1, then you should be able to simply and easily create a
    connection pool to petstore via the console.
    The current error you encountering: "petstorePool does not exist" is
    because either:
    petstorePool is not defined or there was a failure when the pool was first
    created trying to connect to the DBMS.
    The full errror should be in the log file prior to the TXDatasource error.
    Cheers
    mbg
    "Beverly Claire" <[email protected]> wrote in message
    news:[email protected]...
    >
    Hello Rob,
    Thanks for your reply. Yes, the tx datasource's JNDI name isdatasource-petstorePool.
    The server log says that "petstorePool does not exist".
    My conn pool contents:
    Name: petstorePool
    URL: jdbc:oracle:thin:@<replaced with db address>:<replaced with dbport>:<replaced
    with db SID>
    Driver Class Name: oracle.jdbc.driver.OracleDriver
    Properties: user=<replaced with username*>
    password=<replaced with password*>
    *same username and password used to set up the Petstore tables in Oracledb.
    >
    My tx datasource contents:
    Name: PetstoreDataSource
    JNDI: datasource-petstorePool
    Pool Name: petstorePool
    No, actually we're not evaluating in the sense of just-trying-things-out.One
    of our clients is considering an application server. They're relying on usfor
    help in choosing which would be best. As of now, we are comparing BEA WLServer
    7 and 8.1, Sun ONE Application Server 7 EE, Oracle 9i Application Server,and
    Fujitsu Interstage v5 Application Server. For cluster testing andperformance
    comparison purposes, we'd like to use the same J2EE Application across allservers,
    and the obvious choice is Petstore 1.3. One aim is to smoothly connect toan Oracle
    database. The other app servers provide setup scripts and databaseschemas for
    Petstore-with-Oracle, so db conn and deployment are not a problem at all.As for
    WL, we've been trying to get Petstore (both the version downloaded fromSun's
    Java Blueprints and the version that shipped with WL 7) to work withOracle, but
    no luck so far. It's getting a bit frustrating, given the ease with whichthings
    worked out with the other app servers.
    Yes, I've tried out Avitek MedRec for WL 8.1, and this time BEA has kindlymade
    provisions for Oracle db, so connection to Oracle is not a problem. I'mhoping
    BEA will come around to doing the same thing for Petstore, although I'mguessing
    that won't be in the near future.
    Any other suggestions would be much appreciated.
    Thanks,
    Bevery Claire

  • Error while creating creating a prepared statement under WL 6.1

    Hi all,
    can you help please?
    We wrere using weblogic 6.0 with transactions and it worked fine.
    As we switched to weblogic 6.1 sometimes we get the following exception when creating
    a prepared statemnent (first statement after accessing the db connection):
    ERROR: ejbFindByCcProcessorIdActive(1): com.wirecard.io.db.util.DbConnectionException:
    java.sql.SQLException: XA error: XAER_RMERR : A resource manager error has occured
    in the transaction branch start() failed on resource 'weblogic.jdbc.jta.DataSource'
    Internal error during start for XAResource 'wirecardDataPool'
    -at com.wirecard.io.db.util.DbConnection.prepareStatement(Unknown Source)
    The config.xml looks like this:
    <JDBCConnectionPool CapacityIncrement="1" DeploymentOrder="1000"
    DriverName="weblogic.jdbc.oci.xa.XADataSource"
    InitialCapacity="3" JDBCXADebugLevel="0" LoginDelaySeconds="0"
    MaxCapacity="20" Name="testDataPool"
    Properties="user=quintus;weblogic.codeset=UTF8;url=jdbc:weblogic:oracle;password=common;dataSourceName=testDataPool;server=developer;serverName=developer"
    RefreshMinutes="0" ShrinkPeriodMinutes="30"
    ShrinkingEnabled="true" SupportsLocalTransaction="false"
    Targets="localhost" TestConnectionsOnRelease="false"
    TestConnectionsOnReserve="false" URL="jdbc:weblogic:oracle"/>
    <JDBCConnectionPool CapacityIncrement="1" DeploymentOrder="1000"
    DriverName="weblogic.jdbc.oci.xa.XADataSource"
    InitialCapacity="3" JDBCXADebugLevel="0" LoginDelaySeconds="0"
    MaxCapacity="20" Name="testDataPool"
    Properties="user=quintus;weblogic.codeset=UTF8;url=jdbc:weblogic:oracle;password=common;dataSourceName=dataDataPool;server=developer;serverName=developer"
    RefreshMinutes="0" ShrinkPeriodMinutes="30"
    ShrinkingEnabled="true" SupportsLocalTransaction="false"
    Targets="localhost" TestConnectionsOnRelease="false"
    TestConnectionsOnReserve="false" URL="jdbc:weblogic:oracle"/>
    Can anyone help please?
    cu,
    Guenter

    The driver being used by your weblogic is too old and incompatible with the DBMS. Upgrade the driver.

  • XA  error when starting WLS6.1(SP2) with XA connection pools

    I am running WLS6.1 on HPUX11 with an Oracle Database 8.1.7. I am using the XA jDriver/Oracle
    for my connection pools but when I start the server I get the following error:-
    <Apr 25, 2002 6:10:21 PM BST> <Error> <JDBC> <neptune.xenicom.net> <myserver> <main>
    <system> <> <001060> <Cannot startup connection pool "test" weblogic.common.ResourceException:
    java.s
    ql.SQLException: open failed for XAResource 'test' with error XAER_RMERR : A resource
    manager error has occured in the transaction branch. Check Oracle XA trace file(s)
    (if any) for database
    errors. The Oracle XA trace file(s) are located at the directory where you start
    the Weblogic Server, and have names like xa_<pool_name><MMDDYYYY>.trc.
    at weblogic.jdbc.oci.xa.XAConnection.<init>(XAConnection.java:58)
    at weblogic.jdbc.oci.xa.XADataSource.getXAConnection(XADataSource.java:601)
    at weblogic.jdbc.common.internal.XAConnectionEnvFactory.makeConnection(XAConnectionEnvFactory.java:200)
    at weblogic.jdbc.common.internal.XAConnectionEnvFactory.createResource(XAConnectionEnvFactory.java:57)
    at weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllocator.java:698)
    at weblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.java:282)
    at weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.java:623)
    at weblogic.jdbc.common.JDBCService.addDeployment(JDBCService.java:107)
    at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:329)
    at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:279)
    at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:233)
    at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:193)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
    at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
    at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
    at $Proxy29.updateDeployments(Unknown Source)
    at weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(ServerMBean_CachingStub.java:2761)
    at weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(ApplicationManager.java:370)
    at weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManager.java:160)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
    at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
    at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
    at $Proxy38.start(Unknown Source)
    at weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(ApplicationManagerMBean_CachingStub.java:480)
    at weblogic.management.Admin.startApplicationManager(Admin.java:1180)
    at weblogic.management.Admin.finish(Admin.java:590)
    at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:518)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:203)
    at weblogic.Server.main(Server.java:35)
    at weblogic.jdbc.common.internal.XAConnectionEnvFactory.makeConnection(XAConnectionEnvFactory.java:209)
    at weblogic.jdbc.common.internal.XAConnectionEnvFactory.createResource(XAConnectionEnvFactory.java:57)
    at weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllocator.java:698)
    at weblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.java:282)
    at weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.java:623)
    at weblogic.jdbc.common.JDBCService.addDeployment(JDBCService.java:107)
    at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:329)
    at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:279)
    at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:233)
    at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:193)
    I can create a normal (non-X/A) connection pools without any problems however the
    X/A one will just not work at all. I spotted on a goggle newsgroup that someone else
    had this exact same problem but running on WINNT but there was no resolution. The
    following is the trace from the XA trace file:-
    ORACLE XA: Version 8.1.7.0.0. RM name = 'Oracle_XA'.
    181020.21758.1.-662733300:
    xaoopen: xa_info=Oracle_XA+Acc=P/imsi/imsi+SesTm=100+DB=test+Threads=true+LogDir
    =.+DbgFl=0x15,rmid=-662733300,flags=0x0
    181020.21758.1.-662733300:
    ORA-12547: TNS:lost contact
    181020.21758.1.-662733300:
    xaolgn_help: XAER_RMERR; OCIServerAttach failed. ORA-12547.
    181020.21758.1.-662733300:
    xaoopen: return -3
    I have the whole application up and running fine on a WIN2000 platform with its own
    database on the local machine. Also I can point my WIN2000 application to use the
    database on the HPUX11 machine no problem.
    This leads me to think this is a TNS related problem as I cant think of anything
    else !.
    Any help greatly appreciated...!
    Martin

    Hi Martin,
    Using oracles Advanced Security Options can cause this, comment security
    related lines out of your "sqlnet.ora" they generally have the words,
    ENCRYPTION or CRYPTO in them.
    Also try to set ORACLE_SID environment variable, like in the server startup
    script.
    ORACLE_SID=<SID_NAME>
    export ORACLE_SID
    Try it and see if it works. This is purely an Oracle issue not WebLogic
    related. Try to contact Oracle support if you cannot resolve the issue with
    above steps. You may have to reinstall the Client.
    hth
    sree
    "Martin Porter" <[email protected]> wrote in message
    news:[email protected]...
    >
    I am running WLS6.1 on HPUX11 with an Oracle Database 8.1.7. I am usingthe XA jDriver/Oracle
    for my connection pools but when I start the server I get the followingerror:-
    >
    <Apr 25, 2002 6:10:21 PM BST> <Error> <JDBC> <neptune.xenicom.net><myserver> <main>
    <system> <> <001060> <Cannot startup connection pool "test"weblogic.common.ResourceException:
    java.s
    ql.SQLException: open failed for XAResource 'test' with error XAER_RMERR :A resource
    manager error has occured in the transaction branch. Check Oracle XA tracefile(s)
    (if any) for database
    errors. The Oracle XA trace file(s) are located at the directory whereyou start
    the Weblogic Server, and have names like xa_<pool_name><MMDDYYYY>.trc.
    at weblogic.jdbc.oci.xa.XAConnection.<init>(XAConnection.java:58)
    atweblogic.jdbc.oci.xa.XADataSource.getXAConnection(XADataSource.java:601)
    atweblogic.jdbc.common.internal.XAConnectionEnvFactory.makeConnection(XAConnec
    tionEnvFactory.java:200)
    atweblogic.jdbc.common.internal.XAConnectionEnvFactory.createResource(XAConnec
    tionEnvFactory.java:57)
    atweblogic.common.internal.ResourceAllocator.makeResources(ResourceAllocator.j
    ava:698)
    atweblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.java:282
    atweblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.java:623
    atweblogic.jdbc.common.JDBCService.addDeployment(JDBCService.java:107)
    atweblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentT
    arget.java:329)
    atweblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Deployment
    Target.java:279)
    atweblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(D
    eploymentTarget.java:233)
    atweblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(Deploym
    entTarget.java:193)
    at java.lang.reflect.Method.invoke(Native Method)
    atweblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
    .java:636)
    atweblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:6
    21)
    atweblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
    nImpl.java:359)
    atcom.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
    atcom.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
    atweblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
    atweblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
    at $Proxy29.updateDeployments(Unknown Source)
    atweblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(
    ServerMBean_CachingStub.java:2761)
    atweblogic.management.mbeans.custom.ApplicationManager.startConfigManager(Appl
    icationManager.java:370)
    atweblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManage
    r.java:160)
    at java.lang.reflect.Method.invoke(Native Method)
    atweblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
    .java:636)
    atweblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:6
    21)
    atweblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
    nImpl.java:359)
    atcom.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
    atcom.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
    atweblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
    atweblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
    at $Proxy38.start(Unknown Source)
    atweblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(
    ApplicationManagerMBean_CachingStub.java:480)
    atweblogic.management.Admin.startApplicationManager(Admin.java:1180)
    at weblogic.management.Admin.finish(Admin.java:590)
    at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:518)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:203)
    at weblogic.Server.main(Server.java:35)
    atweblogic.jdbc.common.internal.XAConnectionEnvFactory.makeConnection(XAConnec
    tionEnvFactory.java:209)
    atweblogic.jdbc.common.internal.XAConnectionEnvFactory.createResource(XAConnec
    tionEnvFactory.java:57)
    atweblogic.common.internal.ResourceAllocator.makeResources(ResourceAllocator.j
    ava:698)
    atweblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.java:282
    atweblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.java:623
    atweblogic.jdbc.common.JDBCService.addDeployment(JDBCService.java:107)
    atweblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentT
    arget.java:329)
    atweblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Deployment
    Target.java:279)
    atweblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(D
    eploymentTarget.java:233)
    atweblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(Deploym
    entTarget.java:193)
    >
    I can create a normal (non-X/A) connection pools without any problemshowever the
    X/A one will just not work at all. I spotted on a goggle newsgroup thatsomeone else
    had this exact same problem but running on WINNT but there was noresolution. The
    following is the trace from the XA trace file:-
    ORACLE XA: Version 8.1.7.0.0. RM name = 'Oracle_XA'.
    181020.21758.1.-662733300:
    xaoopen:xa_info=Oracle_XA+Acc=P/imsi/imsi+SesTm=100+DB=test+Threads=true+LogDir
    =.+DbgFl=0x15,rmid=-662733300,flags=0x0
    181020.21758.1.-662733300:
    ORA-12547: TNS:lost contact
    181020.21758.1.-662733300:
    xaolgn_help: XAER_RMERR; OCIServerAttach failed. ORA-12547.
    181020.21758.1.-662733300:
    xaoopen: return -3
    I have the whole application up and running fine on a WIN2000 platformwith its own
    database on the local machine. Also I can point my WIN2000 application touse the
    database on the HPUX11 machine no problem.
    This leads me to think this is a TNS related problem as I cant think ofanything
    else !.
    Any help greatly appreciated...!
    Martin

  • Error in obtaining XAConnection from Oracle

    I am unable to create a XAConnection Pool in weblogic. It gives the following error.
    Although with the same settings on NT it works fine.
    JDBC log stream started at Mon Oct 29 16:16:14 GMT-05:00 2001
    Loading library:weblogicoci37
    Finished loading library at:590
    java.sql.SQLException: open failed for XAResource 'XAPool' with error XAER_RMERR
    : A resource manager error has occured in the transaction branch. Check Oracle
    XA trace file(s) (if any) for database errors.
         at weblogic.jdbc.oci.xa.XAConnection.<init>(XAConnection.java:58)
         at weblogic.jdbc.oci.xa.XADataSource.getXAConnection(XADataSource.java:565)
         at weblogic.jdbc.common.internal.XAConnectionEnvFactory.makeConnection(XAConnectionEnvFactory.java:164)
         at weblogic.jdbc.common.internal.XAConnectionEnvFactory.createResource(XAConnectionEnvFactory.java:52)
         at weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllocator.java:653)
         at weblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.java:261)
         at weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.java:695)
         at weblogic.jdbc.common.JDBCService.addDeployment(JDBCService.java:108)
         at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:327)
         at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:277)
         at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:232)
         at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:192)
         at java.lang.reflect.Method.invoke(Native Method)
         at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:562)
         at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:548)
         at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:285)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
         at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:439)
         at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:180)
         at $Proxy31.updateDeployments(Unknown Source)
         at weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(ServerMBean_CachingStub.java:2299)
         at weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(ApplicationManager.java:240)
         at weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManager.java:122)
         at java.lang.reflect.Method.invoke(Native Method)
         at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(Dynamic
    I have weblogic 6.0 running and ORacle 8.1.5 running on two Solaris 7 boxex.
    Oracle is installed under /opt/oracle and weblogic under obt/bea/
    The Path and LD_LIBRARY PATH are set as follows :
    ORACLE_HOME/lib:$ORACLE_HOME/JRE/lib
    ORACLE_BASE=/opt/oracle/app/oracle
    ORACLE_HOME=/opt/oracle/app/oracle/product/8.1.5
    ORACLE_SID=DEV
    PATH=$PATH:$ORACLE_HOME/bin:$ORACLE_HOME/JRE/bin
    export ORACLE_BASE ORACLE_SID ORACLE_HOME PATH
    My Pool settings are
    URL :jdbc:weblogic:oracle:10.224.7.41:1521
    Driver :weblogic.jdbc.oci.xa.XADataSource
    I create a XADataSource using this Pool

    Hi,
    When you have created DSN for the excel spreed sheet you dot not uncheck the read only check box.
    Make sure that the Read Only checkbox is unchecked otherwise you will get an error message while trying to insert data into the Excel spreadsheet (Error: '[Microsoft][ODBC Excel Driver] Operation must use an updateable query.').
    Thanks,
    Sutirtha

  • XA error with Oracle 9.2.0.x / Weblogic 7 sp2

    Hi,
    I have encountered some problems when accessing Oracle 9i (9.2.0.2) via
    Weblogic7 sp2 .
    The problem occurs when a stateless session bean invokes a DAO that get a
    connection from the datasource. The SLSB transaction attribute is set to
    'required'.
    This problem does not when using oracle.driver.OracleDriver or using Oracle
    9.0.1.
    Please help.
    Thanks!
    Regards...
    <JDBCConnectionPool
    DriverName="oracle.jdbc.xa.client.OracleXADataSource"
    InitialCapacity="10" MaxCapacity="10" Name="MyConnectionPool"
    Password="{3DES}EuCgBGHa7vhKa8GfpTjs4w==" Properties="user=psm"
    ShrinkPeriodMinutes="1" ShrinkingEnabled="false"
    SupportsLocalTransaction="false" Targets="myserver"
    URL="jdbc:oracle:thin:@192.168.142.153:1521:oscdev"/>
    <JDBCTxDataSource JNDIName="MyDataSource" Name="MyDataSource"
    PoolName="MyConnectionPool" Targets="myserver"/>
    java.sql.SQLException: XA error: XAER_RMERR : A resource manager error has
    occured in the transaction branch start() failed on resource
    'MyConnectionPool': XAER_RMERR : A resource manager error has occured in the
    transaction branch
    oracle.jdbc.xa.OracleXAException
    at oracle.jdbc.xa.OracleXAResource.checkError(OracleXAResource.java:1157)
    at oracle.jdbc.xa.client.OracleXAResource.start(OracleXAResource.java:295)
    at weblogic.jdbc.jta.VendorXAResource.start(VendorXAResource.java:41)
    at weblogic.jdbc.jta.DataSource.start(DataSource.java:569)
    at
    weblogic.transaction.internal.ServerResourceInfo.start(ServerResourceInfo.ja
    va:1165)
    at
    weblogic.transaction.internal.ServerResourceInfo.xaStart(ServerResourceInfo.
    java:1108)
    at
    weblogic.transaction.internal.ServerResourceInfo.enlist(ServerResourceInfo.j
    ava:287)
    at
    weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTra
    nsactionImpl.java:391)
    at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1143)
    at
    weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1098)
    at weblogic.jdbc.jta.Connection.getXAConn(Connection.java:145)
    at weblogic.jdbc.jta.Connection.prepareStatement(Connection.java:211)
    at
    weblogic.jdbc.rmi.internal.ConnectionImpl.prepareStatement(ConnectionImpl.ja
    va:139)
    at
    weblogic.jdbc.rmi.SerialConnection.prepareStatement(SerialConnection.java:81
    Attached the error log and config.
    [apps.log]
    [config.xml]

    Which version of oracle database are you trying to connect to? we have seen some problems with oracle 920 thin driver. It will be good to use 9013 thin driver instead for now.
    Mitesh
    Wee Hong Ee wrote:
    Hi,
    I have encountered some problems when accessing Oracle 9i (9.2.0.2) via
    Weblogic7 sp2 .
    The problem occurs when a stateless session bean invokes a DAO that get a
    connection from the datasource. The SLSB transaction attribute is set to
    'required'.
    This problem does not when using oracle.driver.OracleDriver or using Oracle
    9.0.1.
    Please help.
    Thanks!
    Regards...
    <JDBCConnectionPool
    DriverName="oracle.jdbc.xa.client.OracleXADataSource"
    InitialCapacity="10" MaxCapacity="10" Name="MyConnectionPool"
    Password="{3DES}EuCgBGHa7vhKa8GfpTjs4w==" Properties="user=psm"
    ShrinkPeriodMinutes="1" ShrinkingEnabled="false"
    SupportsLocalTransaction="false" Targets="myserver"
    URL="jdbc:oracle:thin:@192.168.142.153:1521:oscdev"/>
    <JDBCTxDataSource JNDIName="MyDataSource" Name="MyDataSource"
    PoolName="MyConnectionPool" Targets="myserver"/>
    java.sql.SQLException: XA error: XAER_RMERR : A resource manager error has
    occured in the transaction branch start() failed on resource
    'MyConnectionPool': XAER_RMERR : A resource manager error has occured in the
    transaction branch
    oracle.jdbc.xa.OracleXAException
    at oracle.jdbc.xa.OracleXAResource.checkError(OracleXAResource.java:1157)
    at oracle.jdbc.xa.client.OracleXAResource.start(OracleXAResource.java:295)
    at weblogic.jdbc.jta.VendorXAResource.start(VendorXAResource.java:41)
    at weblogic.jdbc.jta.DataSource.start(DataSource.java:569)
    at
    weblogic.transaction.internal.ServerResourceInfo.start(ServerResourceInfo.ja
    va:1165)
    at
    weblogic.transaction.internal.ServerResourceInfo.xaStart(ServerResourceInfo.
    java:1108)
    at
    weblogic.transaction.internal.ServerResourceInfo.enlist(ServerResourceInfo.j
    ava:287)
    at
    weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTra
    nsactionImpl.java:391)
    at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1143)
    at
    weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1098)
    at weblogic.jdbc.jta.Connection.getXAConn(Connection.java:145)
    at weblogic.jdbc.jta.Connection.prepareStatement(Connection.java:211)
    at
    weblogic.jdbc.rmi.internal.ConnectionImpl.prepareStatement(ConnectionImpl.ja
    va:139)
    at
    weblogic.jdbc.rmi.SerialConnection.prepareStatement(SerialConnection.java:81
    Attached the error log and config.
    Name: apps.log
    apps.log Type: Text Document (application/x-unknown-content-type-txtfile)
    Encoding: x-uuencode
    <?xml version="1.0" encoding="UTF-8"?>
    <!--If your domain is active, please do not edit the config.xml file. Any changes made to that file while the domain is active will not have any effect on the domain's configuration and are likely to be lost. If your domain is inactive, you may edit this file with an XML editor. If you do so, please refer to the BEA Weblogic Server Configuration Reference documentation available from http://edocs.bea.com/wls/docs70/config_xml. In general, we recommend that changes to your configuration file be made through the Administration Console.-->
    <Domain ConfigurationVersion="7.0.0.0" Name="mydomain">
    <Application Deployed="true" Name="DefaultWebApp"
    Path="C:\bea\user_projects\mydomain\applications"
    StagedTargets="" TwoPhase="true">
    <WebAppComponent Name="DefaultWebApp" Targets="myserver" URI="DefaultWebApp"/>
    </Application>
    <Application Deployed="true" Name="certificate"
    Path=".\applications" StagedTargets="" TwoPhase="false">
    <WebAppComponent Name="certificate" Targets="myserver" URI="certificate.war"/>
    </Application>
    <Application Name="poc" Path="D:\HSA\src\deploy\poc.ear"
    StagingMode="nostage" TwoPhase="true">
    <EJBComponent Name="poc-hsa_waf-ejb.jar" Targets="myserver" URI="poc-hsa_waf-ejb.jar"/>
    <EJBComponent Name="user-ejb.jar" Targets="myserver" URI="user-ejb.jar"/>
    <WebAppComponent Name="poc.war/" Targets="myserver" URI="poc.war/"/>
    </Application>
    <ApplicationManager Name="mydomain"/>
    <EmbeddedLDAP
    Credential="{3DES}PMLvNRl/VFtDLKDdfidrUP5bYwm+FAcgdR+UXOY0YiY=" Name="mydomain"/>
    <FileRealm Name="wl_default_file_realm"/>
    <JDBCConnectionPool
    DriverName="oracle.jdbc.xa.client.OracleXADataSource"
    InitialCapacity="10" MaxCapacity="10" Name="MyConnectionPool"
    Password="{3DES}EuCgBGHa7vhKa8GfpTjs4w==" Properties="user=psm"
    ShrinkPeriodMinutes="1" ShrinkingEnabled="false"
    SupportsLocalTransaction="false" Targets="myserver" URL="jdbc:oracle:thin:@192.168.142.153:1521:oscdev"/>
    <JDBCTxDataSource JNDIName="MyDataSource" Name="MyDataSource"
    PoolName="MyConnectionPool" Targets="myserver"/>
    <JTA Name="mydomain"/>
    <Log FileName=".\wl-domain.log" Name="mydomain"/>
    <PasswordPolicy Name="wl_default_password_policy"/>
    <Realm FileRealm="wl_default_file_realm" Name="wl_default_realm"/>
    <SNMPAgent Name="mydomain"/>
    <Security GuestDisabled="false" Name="mydomain"
    PasswordPolicy="wl_default_password_policy"
    Realm="wl_default_realm" RealmSetup="true"/>
    <SecurityConfiguration
    Credential="{3DES}22b8VM1wFkNwKqrWc093vhUk4XsQKkozia+O7H8K4I602imSpWAOlikFQyDOvETIj6mhrD+D+2/Ays3XL4PM//3Y2/TeWxHb" Name="mydomain"/>
    <Server ListenPort="7001" Name="myserver" NativeIOEnabled="true"
    ServerVersion="7.0.0.0" XMLEntityCache="XMLCacheMBean_myserver">
    <COM Name="myserver"/>
    <ExecuteQueue Name="default" ThreadCount="15"/>
    <IIOP Name="myserver"/>
    <JTAMigratableTarget Cluster="" Name="myserver" UserPreferredServer="myserver"/>
    <KernelDebug Name="myserver"/>
    <Log FileName=".\myserver\myserver.log" Name="myserver"/>
    <SSL Enabled="true" HostnameVerificationIgnored="true"
    ListenPort="7002" Name="myserver"
    ServerCertificateChainFileName="ca.pem"
    ServerCertificateFileName="democert.pem" ServerKeyFileName="demokey.pem"/>
    <ServerDebug Name="myserver"/>
    <ServerStart Name="myserver"/>
    <WebServer DefaultWebApp="DefaultWebApp"
    LogFileName=".\myserver\access.log" LoggingEnabled="true" Name="myserver"/>
    </Server>
    <XMLEntityCache Name="XMLCacheMBean_myserver"/>
    </Domain>

  • TWO-PHASE  !!!  XA error  !!! Please help !!!

              Hi Everyone, I am updating 2 databases from 2 different EJBs. I am using ORacle
              XA thing driver oracle.jdbc.xa.client.OracleXADataSource and TX data sources,
              TX connection pools.
              When I start the manager server, I am getting ejb deployment error regarding
              XA driver.
              By the way, in both databases I have taken care of ‘ Grant select on dba_pending_transactions
              to public’ which related to the error XAER_RMERR.
              An error occurred while the EJB container was attempting to obtain information
              a
              bout the table ‘table1’ from the database. This information is necessary
              to validate the mapping between the fields of the EJB 'ejb1' and the table. The
              exception is: XA error: XAER_RMERR : A resource manager error has occur
              ed in the transaction branch start() failed on resource 'jytPool': XAER_RMERR
              A resource manager error has occured in the transaction branch
              javax.transaction.xa.XAException: Unexpected error during start for XAResource
              jytPool': null
              at weblogic.jdbc.jta.XA.createException(XA.java:105)
              at weblogic.jdbc.jta.DataSource.start(DataSource.java:641)
              at weblogic.transaction.internal.ServerResourceInfo.start(ServerResource
              Info.java:1202)
              at weblogic.transaction.internal.ServerResourceInfo.xaStart(ServerResour
              ceInfo.java:1136)
              at weblogic.transaction.internal.ServerResourceInfo.enlist(ServerResourc
              eInfo.java:289)
              at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(Se
              rverTransactionImpl.java:411)
              at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1220)
              at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1
              183)
              at weblogic.jdbc.jta.Connection.getXAConn(Connection.java:152)
              at weblogic.jdbc.jta.Connection.createStatement(Connection.java:257)
              at weblogic.ejb20.utils.TableVerifier.checkTableAndColumns(TableVerifier
              .java:135)
              at weblogic.ejb20.utils.TableVerifier.checkTableAndColumns(TableVerifier
              .java:81)
              at weblogic.ejb20.utils.TableVerifier.verifyTableAndColumnsExist(TableVe
              rifier.java:389)
              at weblogic.ejb20.utils.TableVerifier.verifyTableExistsAndCreateMaybe(Ta
              bleVerifier.java:440)
              at weblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.verifyTablesExist(RD
              BMSPersistenceManager.java:1120)
              at weblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.setup(RDBMSPersisten
              ceManager.java:150)
              at weblogic.ejb20.manager.BaseEntityManager.setupPM(BaseEntityManager.ja
              va:209)
              at weblogic.ejb20.manager.BaseEntityManager.setup(BaseEntityManager.java
              :179)
              at weblogic.ejb20.manager.DBManager.setup(DBManager.java:158)
              at weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.activate(ClientDrive
              nBeanInfoImpl.java:952)
              at weblogic.ejb20.deployer.EJBDeployer.activate(EJBDeployer.java:1317)
              at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:247)
              at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:85)
              at weblogic.j2ee.Application.addComponent(Application.java:307)
              at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:148)
              at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Depl
              oymentTarget.java:375)
              at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Dep
              loymentTarget.java:303)
              at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeploy
              ments(DeploymentTarget.java:256)
              at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(
              DeploymentTarget.java:207)
              at java.lang.reflect.Method.invoke(Native Method)
              at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
              eanImpl.java:750)
              at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
              Please help me in this regard.
              thanks,
              jyothi
              

              What version of Oracle?
              Oracle does not support XA for 8.0.4.
              Oracle 8.1.6 or 8.1.7 supports XA.
              thanks,
              Deepak
              "jyothi" <[email protected]> wrote:
              >
              >Hi Everyone, I am updating 2 databases from 2 different EJBs. I am
              >using ORacle
              >XA thing driver oracle.jdbc.xa.client.OracleXADataSource and TX data
              >sources,
              >TX connection pools.
              >
              >
              >When I start the manager server, I am getting ejb deployment error regarding
              > XA driver.
              >
              >By the way, in both databases I have taken care of ‘ Grant select
              >on dba_pending_transactions
              >to public’ which related to the error XAER_RMERR.
              >
              >An error occurred while the EJB container was attempting to obtain information
              >a
              >bout the table ‘table1’ from the database. This information is necessary
              > to validate the mapping between the fields of the EJB 'ejb1' and the
              >table. The
              >exception is: XA error: XAER_RMERR : A resource manager error has occur
              >ed in the transaction branch start() failed on resource 'jytPool': XAER_RMERR
              >:
              >A resource manager error has occured in the transaction branch
              >javax.transaction.xa.XAException: Unexpected error during start for XAResource
              >'
              >jytPool': null
              > at weblogic.jdbc.jta.XA.createException(XA.java:105)
              > at weblogic.jdbc.jta.DataSource.start(DataSource.java:641)
              > at weblogic.transaction.internal.ServerResourceInfo.start(ServerResource
              >Info.java:1202)
              > at weblogic.transaction.internal.ServerResourceInfo.xaStart(ServerResour
              >ceInfo.java:1136)
              > at weblogic.transaction.internal.ServerResourceInfo.enlist(ServerResourc
              >eInfo.java:289)
              > at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(Se
              >rverTransactionImpl.java:411)
              > at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1220)
              > at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1
              >183)
              > at weblogic.jdbc.jta.Connection.getXAConn(Connection.java:152)
              > at weblogic.jdbc.jta.Connection.createStatement(Connection.java:257)
              > at weblogic.ejb20.utils.TableVerifier.checkTableAndColumns(TableVerifier
              >.java:135)
              > at weblogic.ejb20.utils.TableVerifier.checkTableAndColumns(TableVerifier
              >.java:81)
              > at weblogic.ejb20.utils.TableVerifier.verifyTableAndColumnsExist(TableVe
              >rifier.java:389)
              > at weblogic.ejb20.utils.TableVerifier.verifyTableExistsAndCreateMaybe(Ta
              >bleVerifier.java:440)
              > at weblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.verifyTablesExist(RD
              >BMSPersistenceManager.java:1120)
              > at weblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.setup(RDBMSPersisten
              >ceManager.java:150)
              > at weblogic.ejb20.manager.BaseEntityManager.setupPM(BaseEntityManager.ja
              >va:209)
              > at weblogic.ejb20.manager.BaseEntityManager.setup(BaseEntityManager.java
              >:179)
              > at weblogic.ejb20.manager.DBManager.setup(DBManager.java:158)
              > at weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.activate(ClientDrive
              >nBeanInfoImpl.java:952)
              > at weblogic.ejb20.deployer.EJBDeployer.activate(EJBDeployer.java:1317)
              > at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:247)
              > at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:85)
              > at weblogic.j2ee.Application.addComponent(Application.java:307)
              > at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:148)
              > at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Depl
              >oymentTarget.java:375)
              > at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Dep
              >loymentTarget.java:303)
              > at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeploy
              >ments(DeploymentTarget.java:256)
              > at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(
              >DeploymentTarget.java:207)
              > at java.lang.reflect.Method.invoke(Native Method)
              > at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
              >eanImpl.java:750)
              > at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
              >
              >................................................................
              >
              >
              >Please help me in this regard.
              >thanks,
              >jyothi
              >
              

Maybe you are looking for