XAER_RMERR

I am trying to use Oracle Thin 8.1.7/XA Driver in a distributed Transaction and
while trying to acquire select prepared statement I am getting the following error.
RootCause=[java.sql.SQLException: XA error: XAER_RMERR : A resource manager error
has occured in the transaction branch start() failed on resource 'BeehivePool'
null]
We are using WLS 61 with SP1.
Any help on the issue will be really appreciated.

Hi Sunita,
Make sure instances of oracle are set for XA (initjvm.sql script should
be run on each oracle instance and public select access should be granted to
to dba_pending_transactions. Also check the db version.
Regards,
Slava Imeshev
"Sunita Ajwani" <[email protected]> wrote in message
news:3d57c919$[email protected]..
>
I am trying to use Oracle Thin 8.1.7/XA Driver in a distributedTransaction and
while trying to acquire select prepared statement I am getting thefollowing error.
RootCause=[java.sql.SQLException: XA error: XAER_RMERR : A resource
manager error> has occured in the transaction branch start() failed on resource'BeehivePool'> null
We are using WLS 61 with SP1.
Any help on the issue will be really appreciated.

Similar Messages

Weblogic.transaction.XAException: XAER_RMERR

We have JMS adapter product which uses our own transaction manager to manage an XA global transaction. Using this product we can configure a XA connection and able to produce a message to JMS Queue. Our JMS adapter product works fine with almost all other JMS provider (Sonic, webspere etc) except weblogic. I am using weblogic 9.2. In our code we use to invoke the XAResource() as below
          ((XAQueueSession)queueSession).getXAResource()
          but this throws an error as "can only be called from server". I learnt that in client JVM you can not call getXAResource API directly, rather we should use TxHelper.getClientInterposedTransactionManager(context, serverName). We had introduced following code.
          InterposedTransactionManager itm = TxHelper.getClientInterposedTransactionManager(ctx1, "examplesServer");
          xaResource = itm.getXAResource();
          The above code works fine. Now I am getting XAResource object. But when I produce a message to weblogic JMS Queue, I get the following exception
          weblogic.transaction.XAException: XAER_RMERR : A resource manager error has occured in the transaction branch. ClientTM[examplesServer+172.31.91.57:7001+wl_server+t3+].XAResource.commit() fails.
          at weblogic.transaction.internal.XAResourceHelper.throwXAException(XAResourceHelper.java:172)
          at weblogic.transaction.internal.TransactionManagerImpl$TMXAResource.commit(TransactionManagerImpl.java:993)
          at weblogic.transaction.internal.ClientTransactionManagerImpl$ClientTMXAResource.commit(ClientTransactionManagerImpl.java:136)
          at com.wm.app.b2b.server.jca.transactions.Tran.commit(Tran.java:209)
          at com.wm.app.b2b.server.jca.transactions.Tran.delistResource(Tran.java:482)
          at com.wm.app.b2b.server.jca.transactions.TransactionImpl.delistResource(TransactionImpl.java:89)
          We are using JDK1.5. I am not sure why we are getting the above exception. Our JMS adapter code works fine with almost all other JMS provider even with XA transaction support. The problem is only with Weblogic JMS server.
          Any help on this would be appreciated.
          Thanks,
          Sagar

As per the first exception, XA resource enlistment with foreign TMs is only supported on the server - so you can either use WebLogic transactions, or run the adapter on a WL server. If you'd like to see enhancements in this area, it would help if you contacted WebLogic customer support and asked them to work with the WebLogic JMS product manager (Dave Dabelus).
          Tom

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)

XAER_RMERR with oracle thin 9.0.1.4 and wls 6.1 sp3

I am trying to use Oracle Thin 9.0.1.4 Driver in a distributed Transaction and
while trying to call connection.createStatement() I am getting the
following error.
RootCause=[java.sql.SQLException: XA error: XAER_RMERR : A resource
manager error has occured in the transaction branch start() failed on
resource 'CoreJDBCPool' null]
We are using WLS 6.1SP3
Any help on the issue will be really appreciated
here's the simple test that causes this error
<%@ page isErrorPage="false" errorPage="/common/error.jsp" %>
<%@ page import="javax.sql.DataSource" %>
<%@ page import="java.sql.Connection" %>
<%@ page import="java.sql.Statement" %>
<%@ page import="javax.naming.InitialContext" %>
<%@ page import="javax.transaction.UserTransaction" %>
<html>
<body>
Testing update
 
<%
Statement stmt = null;;
Connection conn = null;
UserTransaction ut = null;
try {
InitialContext ctx = new InitialContext();
// TODO: add the JNDI name for the datasource here
// get the datasource from the app
DataSource ds = (DataSource)ctx.lookup("jdbc/TrueResolutionDB");
ut =(UserTransaction) ctx.lookup("java:comp/UserTransaction");
ut.begin();
if (ds != null){
// Get a connection to the database
conn = ds.getConnection();
// Get a statement from the connection
stmt = conn.createStatement();
// Execute the Update
int rows = stmt.executeUpdate( "update csr_submission set
userid='wilaw' where submissionseq=436");
// Print how many rows were modified
out.println( rows + " Rows modified" ) ;
ut.commit();
} else {
out.println("datasource is null");
catch( Exception e ){
if (ut != null)
ut.rollback();
out.println(e.toString()) ;
e.printStackTrace();
// Close the statement and the connection
if (stmt != null)
stmt.close() ;
if (conn != null)
conn.close() ;
%>

Hi Bala,
Here is what I remembered - I saw this error when a part of the network
connecting weblogic to oracle was misconfigured, so throughput dropped
from 100Mbit/s to somewhat 64Kbit-sec.
When weblogic message level was set to warning, it was showing lots
of pool's connection refreshes. In my case this error was appearing
after some time. The source of the error is that when a weblogic XA
resource is inactive for 2 minutes, the server delists it and everything
goes south. The workaround for this is to have refresh period a bit less
than 2 minutes, or, better, have an operating network infrastructure :)
As for the settings you provided - they are not optimal. The better
configuration would look like this:
<JDBCConnectionPool
CapacityIncrement="0" 
ConnLeakProfilingEnabled="false" 
DriverName="oracle.jdbc.driver.OracleDriver"
InitialCapacity="40" 
LoginDelaySeconds="1"
MaxCapacity="40"
Name="nonXACoreJDBCPool"
Properties="oracle.jdbc.V8Compatible=true;user=bala;password=bala;dll=ocijdb
c9;protocol=thin"
RefreshMinutes="99999" 
Targets="TrueResolutionServer"
TestTableName="CSR_Submission"
URL="jdbc:oracle:thin:@yoshi:1521:hestia"

TestConnectionsOnReserve="true" 
TestTableName="DUAL" 
ShrinkingEnabled="false" 
/>
These settings will give you maximum performance from the pool.
Hope this helps.
Regards,
Slava
"Bala" <[email protected]> wrote in message
news:[email protected]...
>
Hi Slava,
I was hoping for a response from someone like you - I saw you had similarerrors
but did not see the solution :-). In any case, here's my connection pooland datasource
information.
<JDBCTxDataSource EnableTwoPhaseCommit="true"JNDIName="jdbc/TrueResolutionDB"
Name="CoreDataSource" PoolName="CorePool" StreamChunkSize="8192"Targets="TrueResolutionServer"
/>
<JDBCConnectionPool CapacityIncrement="5" ConnLeakProfilingEnabled="true"DriverName="oracle.jdbc.driver.OracleDriver"
InitialCapacity="10" LoginDelaySeconds="1" MaxCapacity="40"Name="nonXACoreJDBCPool"
>
Properties="oracle.jdbc.V8Compatible=true;user=bala;password=bala;dll=ocijdb
c9;protocol=thin"
RefreshMinutes="10" Targets="TrueResolutionServer"TestTableName="CSR_Submission"
URL="jdbc:oracle:thin:@yoshi:1521:hestia" />
as you can see from the entry below the number of execute threads isreasonable
>
<ExecuteQueue Name="default" ThreadCount="15" ThreadPriority="10" />
"Slava Imeshev" <[email protected]> wrote:
Hi Bala.
I remember I had the same problem. Trying to recollect how I fixed it...
Meanwhile, can you post your connection pool and datasource
definitions from your config.xml?
Regards,
Slava Imeshev
"Bala" <[email protected]> wrote in message
news:[email protected]...
I do have the oracle thin driver in the classpath. the failure thatI see
is sporadic
- this makes it worse than a predictable failure. The ThreadCountparameter in
config.xml is set to 15 and the min and max capacity of the
ConnectionPool
is
set to 25 and 40 respectively (high enough, I would think).
Is Oracle Thin 9.0.1.4 Driver in the Classpath variable?
Get Oracle Thin 9.0.1.4 Driver from
http://otn.oracle.com/software/tech/java/sqlj_jdbc/content.html
"Bala" <[email protected]> wrote:
I am trying to use Oracle Thin 9.0.1.4 Driver in a distributed
Transaction
and
while trying to call connection.createStatement() I am getting the
following error.
RootCause=[java.sql.SQLException: XA error: XAER_RMERR : A resource
manager error has occured in the transaction branch start() failedon> >> >>resource 'CoreJDBCPool' null
We are using WLS 6.1SP3
Any help on the issue will be really appreciated
here's the simple test that causes this error
<%@ page isErrorPage="false" errorPage="/common/error.jsp" %>
<%@ page import="javax.sql.DataSource" %>
<%@ page import="java.sql.Connection" %>
<%@ page import="java.sql.Statement" %>
<%@ page import="javax.naming.InitialContext" %>
<%@ page import="javax.transaction.UserTransaction" %>
<html>
<body>
Testing update
 
<%
Statement stmt = null;;
Connection conn = null;
UserTransaction ut = null;
try {
InitialContext ctx = new InitialContext();
// TODO: add the JNDI name for the datasource here
// get the datasource from the app
DataSource ds = (DataSource)ctx.lookup("jdbc/TrueResolutionDB");
ut =(UserTransaction) ctx.lookup("java:comp/UserTransaction");
ut.begin();
if (ds != null){
// Get a connection to the database
conn = ds.getConnection();
// Get a statement from the connection
stmt = conn.createStatement();
// Execute the Update
int rows = stmt.executeUpdate( "update csr_submission set
userid='wilaw' where submissionseq=436");
// Print how many rows were modified
out.println( rows + " Rows modified" ) ;
ut.commit();
} else {
out.println("datasource is null");
catch( Exception e ){
if (ut != null)
ut.rollback();
out.println(e.toString()) ;
e.printStackTrace();
// Close the statement and the connection
if (stmt != null)
stmt.close() ;
if (conn != null)
conn.close() ;
%>

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

XAER_RMERR error when configuring readonly cache group

Hello,
I am having some problem with XA transaction controll on websphere.
error log looks like below.
====================================================================
[09. 6. 26 13:28:15:511 KST] 0000002b ServiceLogger I com.ibm.ws.ffdc.IncidentStreamImpl open FFDC0009I: FFDC가 /was/WebSphere61/AppServer/profiles/AppSrv01/logs/ffdc/server1_0000002b_09.06.26_13.28.15_2.txt 문제 스트림 파일을 열었습니다.
[09. 6. 26 13:28:15:536 KST] 0000002b ServiceLogger I com.ibm.ws.ffdc.IncidentStreamImpl resetIncidentStream FFDC0010I: FFDC가 /was/WebSphere61/AppServer/profiles/AppSrv01/logs/ffdc/server1_0000002b_09.06.26_13.28.15_2.txt 문제 스트림 파일을 닫았습니다.
[09. 6. 26 13:28:15:551 KST] 0000002b ServiceLogger I com.ibm.ws.ffdc.IncidentStreamImpl open FFDC0009I: FFDC가 /was/WebSphere61/AppServer/profiles/AppSrv01/logs/ffdc/server1_0000002b_09.06.26_13.28.15_3.txt 문제 스트림 파일을 열었습니다.
[09. 6. 26 13:28:15:555 KST] 0000002b ServiceLogger I com.ibm.ws.ffdc.IncidentStreamImpl resetIncidentStream FFDC0010I: FFDC가 /was/WebSphere61/AppServer/profiles/AppSrv01/logs/ffdc/server1_0000002b_09.06.26_13.28.15_3.txt 문제 스트림 파일을 닫았습니다.
[09. 6. 26 13:28:15:557 KST] 0000002b RegisteredRes E WTRN0078E: 트랜잭션 관리자가 트랜잭션 자원 시작을 호출하려는 중에 오류가 발생했습니다. 오류 코드는 XAER_RMERR입니다. 예외 스택 추적은 다음과 같습니다: javax.transaction.xa.XAException: errorCode=XAER_RMERR, a resource manager error has occured in the transaction branch.
     at com.timesten.jdbc.xa.XAJdbcOdbc.XAStandardError(XAJdbcOdbc.java:298)
     at com.timesten.jdbc.xa.XAJdbcOdbc.SQLXAStart(XAJdbcOdbc.java:67)
     at com.timesten.jdbc.xa.TimesTenXAResource.start(TimesTenXAResource.java:273)
     at com.ibm.ws.rsadapter.spi.WSRdbXaResourceImpl.start(WSRdbXaResourceImpl.java:1417)
     at com.ibm.ejs.j2c.XATransactionWrapper.start(XATransactionWrapper.java:1467)
     at com.ibm.ws.Transaction.JTA.JTAResourceBase.start(JTAResourceBase.java:145)
     at com.ibm.ws.Transaction.JTA.RegisteredResources.startRes(RegisteredResources.java:1240)
     at com.ibm.ws.Transaction.JTA.RegisteredResources.enlistResource(RegisteredResources.java:648)
     at com.ibm.ws.Transaction.JTA.TransactionImpl.enlistResource(TransactionImpl.java:3294)
     at com.ibm.ws.Transaction.JTA.TranManagerSet.enlist(TranManagerSet.java:405)
     at com.ibm.ejs.j2c.XATransactionWrapper.enlist(XATransactionWrapper.java:693)
     at com.ibm.ejs.j2c.ConnectionManager.lazyEnlist(ConnectionManager.java:1909)
     at com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl.lazyEnlist(WSRdbManagedConnectionImpl.java:2219)
     at com.ibm.ws.rsadapter.jdbc.WSJdbcConnection.beginTransactionIfNecessary(WSJdbcConnection.java:643)
     at com.ibm.ws.rsadapter.jdbc.WSJdbcConnection.prepareStatement(WSJdbcConnection.java:2083)
     at com.ibm.ws.rsadapter.jdbc.WSJdbcConnection.prepareStatement(WSJdbcConnection.java:2038)
     at com.huni.framework.front.dao.HmmDAO.showPrg(HmmDAO.java:181)
     at com.huni.framework.ejbcommand.CommandExecuter.initCommand(CommandExecuter.java:53)
     at com.huni.framework.ejbcommand.CommandExecuter.executeCommand(CommandExecuter.java:27)
     at com.huni.framework.front.bean.HMMFacadeBean.executeCommand(HMMFacadeBean.java:104)
     at com.huni.framework.front.bean.EJSRemoteStatelessHMMFacade_905ddb17.executeCommand(Unknown Source)
     at com.huni.framework.front.bean._HMMFacade_Stub.executeCommand(_HMMFacade_Stub.java:267)
     at com.huni.common.servlet.HmmServlet.doPost(HmmServlet.java:103)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
     at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1143)
     at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:591)
     at com.ibm.ws.wswebcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:481)
     at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3453)
     at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:267)
     at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:815)
     at com.ibm.ws.wswebcontainer.WebContainer.handleRequest(WebContainer.java:1466)
     at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:119)
     at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:458)
     at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:387)
     at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready(HttpInboundLink.java:267)
     at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.sendToDiscriminators(NewConnectionInitialReadCallback.java:214)
     at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.complete(NewConnectionInitialReadCallback.java:113)
     at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:165)
     at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217)
     at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161)
     at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:136)
     at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:196)
     at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:751)
     at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:881)
     at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1473)
=================================================================================
By seeing the similar forum message like this which is saying that XA transactions are not allowed with replication configured, i am wondering whether readonly cache group is relevant with this.
I is not allowed too??
best regards,
Yu-Mi

Cache Connect is not supported with XA transactions. This is mentioned in the Docs, albeit only in the Error Messages section (Error 11037 per my 7.0.3. copy).

Sybase XA XAER_RMERR

Hi,
I am trying to get XA working with Sybase ASE 12. We have the XA license installed and working.
We're using jConnect 6, and get the following error when starting a transaction. Any help would be greatly appreciated.
Do I need to tell Sybase that Weblogic 8.1 is the resource manager? If so, how?
<pre>
java.sql.SQLException: Unexpected exception while enlisting XAConnection java.sql.SQLException: XA error: XAER_RMERR : A resource manager error has occured in the transaction branch start() failed on resource 'tordevfire_scenario': XAER_RMERR : A resource manager error has occured in the transaction branch
javax.transaction.xa.XAException
at com.sybase.jdbc3.jdbc.SybXAResource.sendRPC(Ljava.lang.String;Ljavax.transaction.xa.Xid;III)I(SybXAResource.java:756)
at com.sybase.jdbc3.jdbc.SybXAResource.sendRPC(Ljava.lang.String;Ljavax.transaction.xa.Xid;II)I(SybXAResource.java:647)
at com.sybase.jdbc3.jdbc.SybXAResource.start(Ljavax.transaction.xa.Xid;I)V(SybXAResource.java:312)
at weblogic.jdbc.jta.DataSource.start(Ljavax.transaction.xa.Xid;I)V(DataSource.java:629)
at weblogic.transaction.internal.XAServerResourceInfo.start(Lweblogic.transaction.internal.ServerTransactionImpl;Ljavax.transaction.xa.Xid;I)V(XAServerResourceInfo.java:1140)
at weblogic.transaction.internal.XAServerResourceInfo.xaStart(Lweblogic.transaction.internal.ServerTransactionImpl;I)V(XAServerResourceInfo.java:1072)
at weblogic.transaction.internal.XAServerResourceInfo.enlist(Lweblogic.transaction.internal.ServerTransactionImpl;)Z(XAServerResourceInfo.java:240)
at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(Ljavax.transaction.xa.XAResource;)Z(ServerTransactionImpl.java:463)
at weblogic.jdbc.jta.DataSource.enlist(Lweblogic.transaction.Transaction;)V(DataSource.java:1392)
at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(Lweblogic.jdbc.wrapper.XAConnection;Lweblogic.jdbc.wrapper.JTAConnection;Z)Lweblogic.jdbc.wrapper.XAConnection;(DataSource.java:1334)
at weblogic.jdbc.jta.DataSource.getConnection()Ljava.sql.Connection;(DataSource.java:396)
at weblogic.jdbc.jta.DataSource.connect(Ljava.lang.String;Ljava.util.Properties;)Ljava.sql.Connection;(DataSource.java:354)
at weblogic.jdbc.common.internal.RmiDataSource.getConnection()Ljava.sql.Connection;(RmiDataSource.java:305)
</pre>

What service pack level of 8.1?
thanks
Joe
Craig Pardey wrote:
Hi,
I am trying to get XA working with Sybase ASE 12. We have the XA license installed and working.
We're using jConnect 6, and get the following error when starting a transaction. Any help would be greatly appreciated.
Do I need to tell Sybase that Weblogic 8.1 is the resource manager? If so, how?
<pre>
java.sql.SQLException: Unexpected exception while enlisting XAConnection java.sql.SQLException: XA error: XAER_RMERR : A resource manager error has occured in the transaction branch start() failed on resource 'tordevfire_scenario': XAER_RMERR : A resource manager error has occured in the transaction branch
javax.transaction.xa.XAException
at com.sybase.jdbc3.jdbc.SybXAResource.sendRPC(Ljava.lang.String;Ljavax.transaction.xa.Xid;III)I(SybXAResource.java:756)
at com.sybase.jdbc3.jdbc.SybXAResource.sendRPC(Ljava.lang.String;Ljavax.transaction.xa.Xid;II)I(SybXAResource.java:647)
at com.sybase.jdbc3.jdbc.SybXAResource.start(Ljavax.transaction.xa.Xid;I)V(SybXAResource.java:312)
at weblogic.jdbc.jta.DataSource.start(Ljavax.transaction.xa.Xid;I)V(DataSource.java:629)
at weblogic.transaction.internal.XAServerResourceInfo.start(Lweblogic.transaction.internal.ServerTransactionImpl;Ljavax.transaction.xa.Xid;I)V(XAServerResourceInfo.java:1140)
at weblogic.transaction.internal.XAServerResourceInfo.xaStart(Lweblogic.transaction.internal.ServerTransactionImpl;I)V(XAServerResourceInfo.java:1072)
at weblogic.transaction.internal.XAServerResourceInfo.enlist(Lweblogic.transaction.internal.ServerTransactionImpl;)Z(XAServerResourceInfo.java:240)
at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(Ljavax.transaction.xa.XAResource;)Z(ServerTransactionImpl.java:463)
at weblogic.jdbc.jta.DataSource.enlist(Lweblogic.transaction.Transaction;)V(DataSource.java:1392)
at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(Lweblogic.jdbc.wrapper.XAConnection;Lweblogic.jdbc.wrapper.JTAConnection;Z)Lweblogic.jdbc.wrapper.XAConnection;(DataSource.java:1334)
at weblogic.jdbc.jta.DataSource.getConnection()Ljava.sql.Connection;(DataSource.java:396)
at weblogic.jdbc.jta.DataSource.connect(Ljava.lang.String;Ljava.util.Properties;)Ljava.sql.Connection;(DataSource.java:354)
at weblogic.jdbc.common.internal.RmiDataSource.getConnection()Ljava.sql.Connection;(RmiDataSource.java:305)
</pre>

Intermittent XAER_RMERR on Start Branch/ getConnection()

Hello,
I've been reading the forums on and off for a couple months now. I was hoping someone could help me with a problem I am facing.
I have a Container Managed MDB that persists a message in a DB. I am able to successfully complete a XA Transaction and my DB is setup for XA. I am running Weblogic 8 sp3 and connecting to a Oracle 8.1.7 DB using Oracle 9.0.2 drivers (due to integration reasons).
I ocassionally get the following error. I have "Test Connections on Reserve" and "Test Connections on Release" both checked. My initial Pool size is 0 and I have shrinking allowed. Any thoughts?
javax.ejb.EJBException: nested exception is: java.sql.SQLException: Unexpected exception while enlisting XAConnection java.sql.SQLException: XA error: XAER_RMERR : A resource manager error has occured in the transaction branch start() failed on resource 'SMHPMEConnectionPool': XAER_RMERR : A resource manager error has occured in the transaction branch
javax.transaction.xa.XAException: Unexpected error during start for XAResource 'SMHPMEConnectionPool': Transaction timed out after 61 seconds
Xid=BEA1-20C1A39CB54A5585B43F(32612847),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=61,seconds left=60,XAServerResourceInfo[JMS_SMHPMEJDBCStore]=(ServerResourceInfo[JMS_SMHPMEJDBCStore]=(state=started,assigned=none),xar=JMS_SMHPMEJDBCStore,re-Registered = false),SCInfo[MLIM+mlimManaged2]=(state=active),local properties=({weblogic.jdbc.jta.SMHPMEConnectionPool=weblogic.jdbc.wrapper.TxInfo@be676c}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=mlimManaged2+jasweblp.mlam.ml.com:9104+MLIM+t3+, XAResources={},NonXAResources={})],CoordinatorURL=mlimManaged2+jasweblp.mlam.ml.com:9104+MLIM+t3+)
     at weblogic.jdbc.wrapper.XA.createException(XA.java:104)
     at weblogic.jdbc.jta.DataSource.start(DataSource.java:678)
     at weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1103)
     at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1035)
     at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:213)
     at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:461)
     at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1383)
     at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1325)
     at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:396)
     at weblogic.jdbc.jta.DataSource.connect(DataSource.java:354)
     at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:305)
     at com.ml.mlim.smh.pme.portfolio.j2ee.PMEPortfolioBean.getConnection(Unknown Source)
     at com.ml.mlim.smh.pme.portfolio.j2ee.PMEPortfolioBean.init(Unknown Source)
     at com.ml.mlim.smh.pme.portfolio.j2ee.PMEPortfolioBean.onMessage(Unknown Source)
     at weblogic.ejb20.internal.MDListener.execute(MDListener.java:370)
     at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:262)
     at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2678)
     at weblogic.jms.client.JMSSession.execute(JMSSession.java:2598)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)

You might try upping your JTA Transaction Timeout as well
as XASetTransactionTimeout and XATransactionTimeout; the
latter have to be set manually in the config.xml.
I believe we had similar problems with long-running txns,
and this fixed it.
: jay

Tpopen TPERMERR xa_open returned XAER_RMERR

Trouble during tmboot phase of servers...
Resource management of the database extensions are failing even though the correct
settings (ie. database name, user name/password, and TMS resource/TMSUDB2) are
stated in the tuxedo configuration file. Receive a "CMDTUX_CAT:825" notifying
that the resource did not activate but nothing more (how can the level of debug
information be increased? major problem with tmadmin and debugging).
Also, just prior to tmboot running through the list of groups/servers to boot
an error message related to TMSUDB2 is logged: "LIBTUX_CAT:466: ERROR: tpopen
TPERMERR xa_open returned XAER_RMERR." And the tpsvrinit() fails.
Attached is the ULOG log. I would love some help in learning how to debug resource
errors. I am not educated as a tuxedo sys admin. only a developer.
mvh - Matthew Young
[ULOG.081502]

Matthew,
are you sure the entries in the udataobj/RM file
are correct ?
Peter Holditch <[email protected]> wrote:
Matthew,
You don't need a Tuxedo administrator, you need a database administrator!
Your Tuxedo server calls tpopen() or tx_open(). This in turn calls xa_open()
passing the OPENINFO string you configured for the server group. The
xa_open
function itself is implemented by the database.
XAER_RMERR is the mechanism prescribed by the xa specification for the
RM to
report "I have failed" Tuxedo is passing that information back to you.
You need to use whatever database debugging facilities you have available
to
determine why the database's xa_open routine failed. With Oracle,
you can
enable xa tracing with the OPENINFO. WIth UDB, I have no idea what diagnostics
are available.
I hope that helps!
Peter.
Matthew Young wrote:
Trouble during tmboot phase of servers...
Resource management of the database extensions are failing even thoughthe correct
settings (ie. database name, user name/password, and TMS resource/TMSUDB2)are
stated in the tuxedo configuration file. Receive a "CMDTUX_CAT:825"notifying
that the resource did not activate but nothing more (how can the levelof debug
information be increased? major problem with tmadmin and debugging).
Also, just prior to tmboot running through the list of groups/serversto boot
an error message related to TMSUDB2 is logged: "LIBTUX_CAT:466: ERROR:tpopen
TPERMERR xa_open returned XAER_RMERR." And the tpsvrinit() fails.
Attached is the ULOG log. I would love some help in learning how todebug resource
errors. I am not educated as a tuxedo sys admin. only a developer.
mvh - Matthew Young
143625.W40006071!BBL.645: 081502: TUXEDO Version 6.4 32-bit Windows.
143625.W40006071!BBL.645: LIBTUX_CAT:262: INFO: Standard main starting
143629.W40006071!TMS.616: 081502: TUXEDO Version 6.4 32-bit Windows.
143629.W40006071!TMS.616: LIBTUX_CAT:262: INFO: Standard main starting
143629.W40006071!TMS.639: 081502: TUXEDO Version 6.4 32-bit Windows.
143629.W40006071!TMS.639: LIBTUX_CAT:262: INFO: Standard main starting
143629.W40006071!TMS.471: 081502: TUXEDO Version 6.4 32-bit Windows.
143629.W40006071!TMS.471: LIBTUX_CAT:262: INFO: Standard main starting
143629.W40006071!TMS.630: 081502: TUXEDO Version 6.4 32-bit Windows.
143629.W40006071!TMS.630: LIBTUX_CAT:262: INFO: Standard main starting
143629.W40006071!TMS.515: 081502: TUXEDO Version 6.4 32-bit Windows.
143629.W40006071!TMS.515: LIBTUX_CAT:262: INFO: Standard main starting
143629.W40006071!TMS.359: 081502: TUXEDO Version 6.4 32-bit Windows.
143629.W40006071!TMS.359: LIBTUX_CAT:262: INFO: Standard main starting
143630.W40006071!TMSUDB2.643: 081502: TUXEDO Version 6.4 32-bit Windows.
143630.W40006071!TMSUDB2.643: LIBTUX_CAT:262: INFO: Standard main starting
143630.W40006071!TMSUDB2.643: LIBTUX_CAT:466: ERROR: tpopen TPERMERRxa_open returned XAER_RMERR
143630.W40006071!TMSUDB2.643: LIBTUX_CAT:250: ERROR: tpsvrinit() failed
143630.W40006071!tmboot.478: 081502: TUXEDO Version 6.4 32-bit Windows.
143630.W40006071!tmboot.478: CMDTUX_CAT:825: ERROR: Process TMSUDB2at LOCALPC failed with /T tperrno (TPERMERR - resource manager error)
143630.W40006071!TMSUDB2.531: 081502: TUXEDO Version 6.4 32-bit Windows.
143630.W40006071!TMSUDB2.531: LIBTUX_CAT:262: INFO: Standard main starting
143630.W40006071!TMSUDB2.531: LIBTUX_CAT:466: ERROR: tpopen TPERMERRxa_open returned XAER_RMERR
143630.W40006071!TMSUDB2.531: LIBTUX_CAT:250: ERROR: tpsvrinit() failed
143630.W40006071!tmboot.478: CMDTUX_CAT:825: ERROR: Process TMSUDB2at LOCALPC failed with /T tperrno (TPERMERR - resource manager error)
143630.W40006071!TMSUDB2.341: 081502: TUXEDO Version 6.4 32-bit Windows.
143630.W40006071!TMSUDB2.341: LIBTUX_CAT:262: INFO: Standard main starting
143630.W40006071!TMSUDB2.341: LIBTUX_CAT:466: ERROR: tpopen TPERMERRxa_open returned XAER_RMERR
143630.W40006071!TMSUDB2.341: LIBTUX_CAT:250: ERROR: tpsvrinit() failed
143630.W40006071!tmboot.478: CMDTUX_CAT:825: ERROR: Process TMSUDB2at LOCALPC failed with /T tperrno (TPERMERR - resource manager error)
143630.W40006071!TMSUDB2.427: 081502: TUXEDO Version 6.4 32-bit Windows.
143630.W40006071!TMSUDB2.427: LIBTUX_CAT:262: INFO: Standard main starting
143630.W40006071!TMSUDB2.427: LIBTUX_CAT:466: ERROR: tpopen TPERMERRxa_open returned XAER_RMERR
143630.W40006071!TMSUDB2.427: LIBTUX_CAT:250: ERROR: tpsvrinit() failed
143630.W40006071!tmboot.478: CMDTUX_CAT:825: ERROR: Process TMSUDB2at LOCALPC failed with /T tperrno (TPERMERR - resource manager error)
143631.W40006071!DMADM.474: 081502: TUXEDO Version 6.4 32-bit Windows.
143631.W40006071!DMADM.474: LIBTUX_CAT:262: INFO: Standard main starting
143631.W40006071!DMADM.474: CMDGW_CAT:3149: INFO: BDMCONFIG environmentvariable not set. Using $APPDIR/BDMCONFIG
143631.W40006071!GWADM.596: 081502: TUXEDO Version 6.4 32-bit Windows.
143631.W40006071!GWADM.596: LIBTUX_CAT:262: INFO: Standard main starting
143631.W40006071!DMADM.474: CMDGW_CAT:3142: ERROR: Cannot send configto GWADM group=DOM_GW
143631.W40006071!GWADM.596: LIBTUX_CAT:250: ERROR: tpsvrinit() failed
143631.W40006071!tmboot.478: CMDTUX_CAT:825: ERROR: Process GWADM atLOCALPC failed with /T tperrno (TPESVCFAIL - application level service
failure)
143631.W40006071!TMS.467: 081502: TUXEDO Version 6.4 32-bit Windows.
143631.W40006071!TMS.467: LIBTUX_CAT:262: INFO: Standard main starting
143631.W40006071!TMS.406: 081502: TUXEDO Version 6.4 32-bit Windows.
143631.W40006071!TMS.406: LIBTUX_CAT:262: INFO: Standard main starting
143632.W40006071!meddelandeadmv.603: 081502: TUXEDO Version 6.4 32-bitWindows.
143632.W40006071!meddelandeadmv.603: LIBTUX_CAT:262: INFO: Standardmain starting
143632.W40006071!TMSUDB2.429: 081502: TUXEDO Version 6.4 32-bit Windows.
143632.W40006071!TMSUDB2.429: LIBTUX_CAT:262: INFO: Standard main starting
143632.W40006071!TMSUDB2.429: LIBTUX_CAT:466: ERROR: tpopen TPERMERRxa_open returned XAER_RMERR
143632.W40006071!TMSUDB2.429: LIBTUX_CAT:250: ERROR: tpsvrinit() failed
143632.W40006071!tmboot.478: CMDTUX_CAT:825: ERROR: Process TMSUDB2at LOCALPC failed with /T tperrno (TPERMERR - resource manager error)
143632.W40006071!TMSUDB2.435: 081502: TUXEDO Version 6.4 32-bit Windows.
143632.W40006071!TMSUDB2.435: LIBTUX_CAT:262: INFO: Standard main starting
143632.W40006071!TMSUDB2.435: LIBTUX_CAT:466: ERROR: tpopen TPERMERRxa_open returned XAER_RMERR
143632.W40006071!TMSUDB2.435: LIBTUX_CAT:250: ERROR: tpsvrinit() failed
143632.W40006071!tmboot.478: CMDTUX_CAT:825: ERROR: Process TMSUDB2at LOCALPC failed with /T tperrno (TPERMERR - resource manager error)
143633.W40006071!sakerhet.425: 081502: TUXEDO Version 6.4 32-bit Windows.
143633.W40006071!sakerhet.425: LIBTUX_CAT:262: INFO: Standard mainstarting
143633.W40006071!sakerhet.425: LIBTUX_CAT:466: ERROR: tpopen TPERMERRxa_open returned XAER_RMERR
143634.W40006071!meddelandeadmi.397: 081502: TUXEDO Version 6.4 32-bitWindows.
143634.W40006071!meddelandeadmi.397: LIBTUX_CAT:262: INFO: Standardmain starting
143634.W40006071!meddelandeadmi.397: LIBTUX_CAT:466: ERROR: tpopenTPERMERR xa_open returned XAER_RMERR
143634.W40006071!fellogg.477: 081502: TUXEDO Version 6.4 32-bit Windows.
143634.W40006071!fellogg.477: LIBTUX_CAT:262: INFO: Standard main starting
143634.W40006071!fellogg.477: LIBTUX_CAT:466: ERROR: tpopen TPERMERRxa_open returned XAER_RMERR
143634.W40006071!meddelandeinfo.465: 081502: TUXEDO Version 6.4 32-bitWindows.
143634.W40006071!meddelandeinfo.465: LIBTUX_CAT:262: INFO: Standardmain starting
143634.W40006071!meddelandeinfo.465: LIBTUX_CAT:466: ERROR: tpopenTPERMERR xa_open returned XAER_RMERR
143834.W40006071!TMS.406: CMDTUX_CAT:457: INFO: TMS tpsvrdone complete
143834.W40006071!TMS.467: CMDTUX_CAT:457: INFO: TMS tpsvrdone complete
143834.W40006071!DMADM.474: CMDGW_CAT:1655: INFO: DMADMSVR is exiting
143834.W40006071!TMS.359: CMDTUX_CAT:457: INFO: TMS tpsvrdone complete
143834.W40006071!TMS.515: CMDTUX_CAT:457: INFO: TMS tpsvrdone complete
143834.W40006071!TMS.630: CMDTUX_CAT:457: INFO: TMS tpsvrdone complete
143834.W40006071!TMS.471: CMDTUX_CAT:457: INFO: TMS tpsvrdone complete
143834.W40006071!TMS.639: CMDTUX_CAT:457: INFO: TMS tpsvrdone complete
143834.W40006071!TMS.616: CMDTUX_CAT:457: INFO: TMS tpsvrdone complete
143838.W40006071!BBL.645: CMDTUX_CAT:26: INFO: The BBL is exiting system
144646.W40006071!tmadmin.351: 081502: TUXEDO Version 6.4 32-bit Windows.
144646.W40006071!tmadmin.351: TMADMIN_CAT:1330: INFO: Command: help

Urgency question, xa_start returned XAER_RMERR

i have an urgency question,
tuxedo 6.5, oracle 8.1.7
when I used tpcall to call a service, which is in a server, tperrno returned 10(TPESVCERR).
The service hase only one select statement as 'EXEC SQL select ...'.
The ULOG file infomation :
082123.nznode4!cserv_v3.105788: gtrid x10001 x3eac9994 x9d: LIBTUX_CAT:481:
ERROR: Service xa_start returned XAER_RMERR
xa_NULL042803.trc
ORACLE XA: Version 8.1.7.0.0. RM name = 'Oracle_XA'.
083014.95804.0:
ORA-24784: Transaction exists
RM file
Oracle_XA:xaosw:-L${ORACLE_HOME}/lib -lm -lclntsh -lsql
and what puzzled me greatly is
when i boot it, it worked well, several minutes later, it worked wrong.
what's the problem? who can help me?
urgency, very thanks.

i have an urgency question,
tuxedo 6.5, oracle 8.1.7
when I used tpcall to call a service, which is in a server, tperrno returned 10(TPESVCERR).
The service hase only one select statement as 'EXEC SQL select ...'.
The ULOG file infomation :
082123.nznode4!cserv_v3.105788: gtrid x10001 x3eac9994 x9d: LIBTUX_CAT:481:
ERROR: Service xa_start returned XAER_RMERR
xa_NULL042803.trc
ORACLE XA: Version 8.1.7.0.0. RM name = 'Oracle_XA'.
083014.95804.0:
ORA-24784: Transaction exists
RM file
Oracle_XA:xaosw:-L${ORACLE_HOME}/lib -lm -lclntsh -lsql
and what puzzled me greatly is
when i boot it, it worked well, several minutes later, it worked wrong.
what's the problem? who can help me?
urgency, very thanks.

Unable to boot bankapp servers with Oracle 8.1.7 in windows2000

Hello,I tried to run bankapp examples with oracle 8.1.7 in windows2000. But when
I booted the servers using tmboot, there are some errors.(1)I used the following
RM entries:Oracle_XA;xaosw;D:\Oracle\Ora81\precomp\lib\msvc\oraSQL8.lib D:\Oracle\Ora81\precomp\lib\msvc\oraSQX8.lib
D:\Oracle\Ora81\RDBMS\xa\ORAXA8.lib (2)The OPENINFO string in the ubbshm file
is:DEFAULT:TMSNAME=TMS_ORA TMSCOUNT=2 LMID=SITE1
BANKB1 GRPNO=1 OPENINFO="Oracle_XA:Oracle_XA+Acc=P/scott/tiger+SesTm=100+LogDir=.+MaxCur=5"(3)the
follow is the error message when I booted the servers:
.. 174841.GLOBALDB!BALC.852.2572.0: 07-26-2001: Tuxedo Version 8.0 32-bit Windows.
174841.GLOBALDB!BALC.852.2572.0: LIBTUX_CAT:262: INFO: Standard main starting
174841.GLOBALDB!BALC.852.2572.0: LIBTUX_CAT:466: ERROR: tpopen TPERMERR xa_open
returned XAER_RMERR
174841.GLOBALDB!BALC.852.2572.0: tpsvrinit: failed to open database due to
174841.GLOBALDB!BALC.852.2572.0: tpopen failed, tperrno: 16
174841.GLOBALDB!BALC.852.2572.0: LIBTUX_CAT:250: ERROR: tpsvrinit() failed
174841.GLOBALDB!tmboot.480.548.-2: CMDTUX_CAT:825: ERROR: Process BALC at SITE1
failed with /T tperrno (TPERMERR - resource manager error) ...
Can anyone help? Thanks a lot!
Best Regards
Lily

I found the answer myself in an earlier post.
<BLOCKQUOTE>quote:<HR>Originally posted by The Oracle Reports Team:
Reports 6i will connect to Oracle8i, however you need to connect over Net8 - i.e. on the database side, you need to set up the TNS listener to accept connections, and on the Reports side (which, incidentally, needs to be installed in a separate Oracle_home) you need to configure the tnsnames.ora file to connect to the 'remote' database (since it is in a different oracle_home, to all intents and purposes it may as well be on another machine - it's all considered 'remote').
Regards
The Oracle Reports Team http://technet.oracle.com <HR></BLOCKQUOTE>
null

Unable to load catalog in CRS application. Indexing is failed

Unable to load catalog in CRS application, Indexation failed: Below is the error msg
**** Error /atg/dynamo/service/jdbc/JTDataSource Unable to connect to data source because of SQLException: Unexpected exception while enlisting XAConnection java.sql.SQLException: XA error: XAResource.XAER_RMERR start() failed on resource 'ATGProductionDS_base_domain': XAER_RMERR : A resource manager error has occured in the transaction branch
**** Error Mon Apr 21 10:35:29 IST 2014 1398056729516 /atg/dynamo/service/jdbc/JTDataSource weblogic.transaction.internal.ResourceAccessException: Transaction has timed out when making request to XAResource 'ATGProductionDS_base_domain'.
**** Error /atg/dynamo/service/jdbc/JTDataSource at weblogic.transaction.internal.XAResourceDescriptor.startResourceUse(XAResourceDescriptor.java:670)
**** Error /atg/dynamo/service/jdbc/JTDataSource at weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1230)
**** Error /atg/dynamo/service/jdbc/JTDataSource at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1164)
Caused by: weblogic.transaction.internal.TimedOutException: Transaction has timed out when making request to XAResource 'ATGProductionDS_base_domain'.
**** Error /atg/dynamo/service/jdbc/JTDataSource at weblogic.transaction.internal.XAResourceDescriptor.startResourceUse(XAResourceDescriptor.java:673)
**** Error /atg/dynamo/service/jdbc/JTDataSource
In Dyn Admin "atg/commerce/search/ProductCatalogOutputConfig" is failed
"atg/commerce/endeca/index/CategoryToDimensionOutputConfig" is failed

This issue is related to weblogic transaction timeout.
Can you increase the weblogic domain transaction timeout?
By default it is 30 sec, increase to 600
Refer Domain --&gt; Configuration --&gt; JTA to increase timeout.
Peace
Shaik

XAER_RMERR

Similar Messages

Maybe you are looking for