Websphere 5.0 & JDBC : LocalTransaction rolled-back due to setRollbackOnly.

Hello,
I'm using WAS 5.0 & Oracle. I'm getting following error.
Resource cp_fcatretail_user_A1 rolled back in cleanup of unresolved LocalTransactionContainment.
LocalTranCoor E WLTC0032E: One or more resources rolled back. An unresolved LocalTransactionContainment had an unresolved action of rollback.
*5258e643 WebAppTransac E WTRN0043I: LocalTransaction rolled-back due to setRollbackOnly.*
*[Servlet Error]-[LocalTransaction rolled-back due to setRollbackOnly]: com.ibm.ws.LocalTransaction.RolledbackException*
at com.ibm.ws.LocalTransaction.LocalTranCoordImpl.cleanup(LocalTranCoordImpl.java:1091)
Plz help me out.
Thanks in Advance
Edited by: PremInd on Dec 27, 2007 2:44 PM

PremInd wrote:
No.. I have wriiten all transaction correctly.
WAS seems to disagree with you.
I think , this problem related to WAS configuration.Aren't your transactions declarative? That is configuration.
Please any one have idea, come forward.All you jokers with nothing to say take one step back.
%

Similar Messages

Transaction roll back exception in setRollbackOnly in stateless bean

Hello All,
Im using WLS 5.1 SP9 on Win2k with Oracle 8.
Flow:
A stateless session bean with container-managed transaction uses
entity beans to insert records into 3 tables, vide:
Primary - CMP,
Secondary - BMP,
Tertiary - CMP
If validation fails on the data thats coming in, error messages are
sent back to the client and the transaction is set to roll back with
the folliwng stmt :
sessionContext.setRollbackOnly();
Now there are 2 problems :
1. Valid data is passed in: Though the operation seems to succeed from
the front end, there aren't any records inserted into the Primary
table. Secondary and Tertiary tables have the right data present in
them.
2. Invalid data is passed in: When the validation fails and the
transaction is set to rollback, the following exceptions are thrown :
Exception during commit of transaction: '1030642768442_27'
weblogic.transaction.RollbackException: Transaction TxC (26691678, xid
= 1030642768442_27, timeout = 60, txState = Rolledback, root = null
has been rolled back.Reason: Unknown

I searched this ng for previous posts on this problema and indeed
found quite a few with the same problem. However, they referred to
this problem as a bug in the earlier service packs of Weblogic such as
4 and 5. I however use SP9, but still get the same problem.
Anybody have any ideas on these problems and possible solutions?
Thanks and regards,
Pavan

The problem seems to be related to the Adapter Engine but not sure about the exact reason. As per the last line of the log, either the channel reference was missing or there was some problem with the related service which could be viewed in visual admin. This could have occurred when the channel is initialized for the use. Restart helped because it may have restarted the related services.
Regards,
Prateek

ATV2 OFFICIALLY rolled back to 4.2.1 due to wireless N issues

My ATV prompted me to update it an hr ago, I did, and when it came back up, 4.3 was gone and 4.2.1 was there.. I plugged it into itunes and it said it was up to date... I called apple support and they verified that JUST the ATV2 has been rolled back due to Wireless N and other wireless compatability issues.

TallBearNC wrote:
I had 4.3 on my ATV for weeks. it even said 4.3 in the about screen. You do not know what YOU are talking about.
Once my ATV went to 4.3 a few weeks ago, it could no longer connect to my N network until I turned WMM on, and even then it kept dropped off. So I had to switch my router back to A/G mode.
Yes, there WAS.. and if you don't belive me, ill be HAPPY to show you the ATV2 4.3 IPSW I've had sitting on my desktop for weeks
You are wrong. Take my advice and stop now before you embarrass yourself.

Transaction not rolled back

          Configuration:
          - WLS 5.10 SP8
          - Oracle 8.1.6
          - TX DataSource connected to a Connection pool of oracle JDBC connections
          I have a stateless session with a method register() that performs three insert operations in the oracle database via a connection fetched from tha TX Datasource object.
          The method register has been marked with the transaction attribute required.
          I recieve a SQLException from Oracle when trying to insert in one of the three tables and want to rollback the transaction.
          I have tried to use setRollBackOnly(), throw an EJB exception
          and i get the following message from WLS:
          java.sql.SQLException: ORA-00001: unique constraint (ISACOWN.UK_ISIS_REFERENCE2) violated
          at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:114)
          at oracle.jdbc.oci8.OCIDBAccess.check_error(OCIDBAccess.java, Compiled Code)
          at oracle.jdbc.oci8.OCIDBAccess.executeFetch(OCIDBAccess.java, Compiled Code)
          at oracle.jdbc.oci8.OCIDBAccess.parseExecuteFetch(OCIDBAccess.java:1235)
          at oracle.jdbc.driver.OracleStatement.executeNonQuery(OracleStatement.java, Compiled Code)
          at oracle.jdbc.driver.OracleStatement.doExecuteOther(OracleStatement.java:1232)
          at oracle.jdbc.driver.OracleStatement.doExecuteWithBatch(OracleStatement.java:1353)
          at oracle.jdbc.driver.OracleStatement.doExecute(OracleStatement.java, Compiled Code)
          at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java, Compiled Code)
          at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java, Compiled Code)
          at weblogic.jdbc20.pool.PreparedStatement.executeUpdate(PreparedStatement.java:47)
          at weblogic.jdbc20.rmi.internal.PreparedStatementImpl.executeUpdate(PreparedStatementImpl.java:54)
          at weblogic.jdbc20.rmi.SerialPreparedStatement.executeUpdate(SerialPreparedStatement.java:55)
          at net.astrazeneca.cmi.data.Crud.execDML(Crud.java:283)
          at net.astrazeneca.cmi.data.dao.MolStructDAO.insertIsisRef(MolStructDAO.java:136)
          at net.astrazeneca.cmi.data.dao.MolStructDAO.insert(MolStructDAO.java, Compiled Code)
          at net.astrazeneca.cmi.data.dataservice.MolStructureDS.register(MolStructureDS.java, Compiled Code)
          at net.astrazeneca.cmi.data.dataservice.MolStructureDSEOImpl.register(MolStructureDSEOImpl.java, Compiled Code)
          at net.astrazeneca.cmi.data.dataservice.MolStructureDSEOImpl_WLSkel.invoke(MolStructureDSEOImpl_WLSkel.java, Compiled Code)
          at weblogic.rmi.extensions.BasicServerObjectAdapter.invoke(BasicServerObjectAdapter.java, Compiled Code)
          at weblogic.rmi.extensions.BasicRequestHandler.handleRequest(BasicRequestHandler.java, Compiled Code)
          at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java, Compiled Code)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled Code)
          ti jan 23 11:12:20 GMT+01:00 2001:<I> <EJB JAR deployment F:\Projects\MolStructureDS\MolStructureDS.jar> Transaction: '980237619834_1326' rolled back
          due to EJB exception:
          javax.ejb.EJBException
          at net.astrazeneca.cmi.data.dataservice.MolStructureDS.register(MolStructureDS.java, Compiled Code)
          Anybody got an idea ? at net.astrazeneca.cmi.data.dataservice.MolStructureDSEOImpl.register(MolStructureDSEOImpl.java, Compiled Code)
          at net.astrazeneca.cmi.data.dataservice.MolStructureDSEOImpl_WLSkel.invoke(MolStructureDSEOImpl_WLSkel.java, Compiled Code)
          at weblogic.rmi.extensions.BasicServerObjectAdapter.invoke(BasicServerObjectAdapter.java, Compiled Code)
          at weblogic.rmi.extensions.BasicRequestHandler.handleRequest(BasicRequestHandler.java, Compiled Code)
          at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java, Compiled Code)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled Code)
          ti jan 23 11:12:20 GMT+01:00 2001:<E> <Adapter> Exception thrown by rmi server: [-3565031217135527434S157.96.215.53:[7001,7001,7002,7002,7001,-1]/466]
          javax.ejb.EJBException
          at net.astrazeneca.cmi.data.dataservice.MolStructureDS.register(MolStructureDS.java, Compiled Code)
          at net.astrazeneca.cmi.data.dataservice.MolStructureDSEOImpl.register(MolStructureDSEOImpl.java, Compiled Code)
          at net.astrazeneca.cmi.data.dataservice.MolStructureDSEOImpl_WLSkel.invoke(MolStructureDSEOImpl_WLSkel.java, Compiled Code)
          at weblogic.rmi.extensions.BasicServerObjectAdapter.invoke(BasicServerObjectAdapter.java, Compiled Code)
          at weblogic.rmi.extensions.BasicRequestHandler.handleRequest(BasicRequestHandler.java, Compiled Code)
          at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java, Compiled Code)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled Code)
          No matter what I have tried so far the two inserts that are OK are commited in Oracle. What I want is to make all three inserts in the transaction rolled back.
          Anybody got an idea ?


          Yes, all through the same connection and the connection is from a TX data source in
          WLS 5.1 with SP8
          But.... I do NOT fetch the connection inside the transaction..but I didn't think
          that was nescessery... is it ?
          When I tried this and checked the JDBC log the auto-commit was turned to off and
          everything worked smoothly.
          /Paul
          "Cameron Purdy" <[email protected]> wrote:
          >All through the same connection? And the connection is from a tx data
          >source? And auto-commit is off?
          >
          >If so, then someone is committing the transaction.
          >
          >Is this 5.1?
          >
          >--
          >Cameron Purdy
          >Tangosol, Inc.
          >http://www.tangosol.com
          >+1.617.623.5782
          >WebLogic Consulting Available
          >
          >
          >"Paul Eriksson" <[email protected]> wrote in message
          >news:[email protected]...
          >>
          >> I've already tried this but still... the tho first inserts are commited
          >and the third that causes the rollback of course is not.
          >>
          >> /P
          >>
          >> "Cameron Purdy" <[email protected]> wrote:
          >> >Don't set rollback only, just throw a runtime exception (like
          >EJBException).
          >> >
          >> >--
          >> >Cameron Purdy
          >> >Tangosol, Inc.
          >> >http://www.tangosol.com
          >> >+1.617.623.5782
          >> >WebLogic Consulting Available
          >> >
          >> >
          >> >"Paul Eriksson" <[email protected]> wrote in message
          >> >news:[email protected]...
          >> >>
          >> >> Configuration:
          >> >>
          >> >> - WLS 5.10 SP8
          >> >> - Oracle 8.1.6
          >> >> - TX DataSource connected to a Connection pool of oracle JDBC
          >connections
          >> >>
          >> >> I have a stateless session with a method register() that performs three
          >> >insert operations in the oracle database via a connection fetched from
          >tha
          >> >TX Datasource object.
          >> >>
          >> >> The method register has been marked with the transaction attribute
          >> >required.
          >> >>
          >> >> I recieve a SQLException from Oracle when trying to insert in one of
          >the
          >> >three tables and want to rollback the transaction.
          >> >>
          >> >>
          >> >> I have tried to use setRollBackOnly(), throw an EJB exception
          >> >> and i get the following message from WLS:
          >> >>
          >> >>
          >> >> java.sql.SQLException: ORA-00001: unique constraint
          >> >(ISACOWN.UK_ISIS_REFERENCE2) violated
          >> >>
          >> >> at
          >> >oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:114)
          >> >> at oracle.jdbc.oci8.OCIDBAccess.check_error(OCIDBAccess.java,
          >> >Compiled Code)
          >> >> at oracle.jdbc.oci8.OCIDBAccess.executeFetch(OCIDBAccess.java,
          >> >Compiled Code)
          >> >> at
          >> >oracle.jdbc.oci8.OCIDBAccess.parseExecuteFetch(OCIDBAccess.java:1235)
          >> >> at
          >> >oracle.jdbc.driver.OracleStatement.executeNonQuery(OracleStatement.java,
          >> >Compiled Code)
          >> >> at
          >>
          >>oracle.jdbc.driver.OracleStatement.doExecuteOther(OracleStatement.java:1232
          >)
          >> >> at
          >>
          >>oracle.jdbc.driver.OracleStatement.doExecuteWithBatch(OracleStatement.java:
          >1
          >> >353)
          >> >> at
          >> >oracle.jdbc.driver.OracleStatement.doExecute(OracleStatement.java,
          >Compiled
          >> >Code)
          >> >> at
          >>
          >>oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.jav
          >a
          >> >, Compiled Code)
          >> >> at
          >>
          >>oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStat
          >e
          >> >ment.java, Compiled Code)
          >> >> at
          >>
          >>weblogic.jdbc20.pool.PreparedStatement.executeUpdate(PreparedStatement.java
          >:
          >> >47)
          >> >> at
          >>
          >>weblogic.jdbc20.rmi.internal.PreparedStatementImpl.executeUpdate(PreparedSt
          >a
          >> >tementImpl.java:54)
          >> >> at
          >>
          >>weblogic.jdbc20.rmi.SerialPreparedStatement.executeUpdate(SerialPreparedSta
          >t
          >> >ement.java:55)
          >> >> at net.astrazeneca.cmi.data.Crud.execDML(Crud.java:283)
          >> >> at
          >>
          >>net.astrazeneca.cmi.data.dao.MolStructDAO.insertIsisRef(MolStructDAO.java:1
          >3
          >> >6)
          >> >> at
          >> >net.astrazeneca.cmi.data.dao.MolStructDAO.insert(MolStructDAO.java,
          >Compiled
          >> >Code)
          >> >> at
          >>
          >>net.astrazeneca.cmi.data.dataservice.MolStructureDS.register(MolStructureDS
          >..
          >> >java, Compiled Code)
          >> >> at
          >>
          >>net.astrazeneca.cmi.data.dataservice.MolStructureDSEOImpl.register(MolStruc
          >t
          >> >ureDSEOImpl.java, Compiled Code)
          >> >> at
          >>
          >>net.astrazeneca.cmi.data.dataservice.MolStructureDSEOImpl_WLSkel.invoke(Mol
          >S
          >> >tructureDSEOImpl_WLSkel.java, Compiled Code)
          >> >> at
          >>
          >>weblogic.rmi.extensions.BasicServerObjectAdapter.invoke(BasicServerObjectAd
          >a
          >> >pter.java, Compiled Code)
          >> >> at
          >>
          >>weblogic.rmi.extensions.BasicRequestHandler.handleRequest(BasicRequestHandl
          >e
          >> >r.java, Compiled Code)
          >> >> at
          >>
          >>weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java,
          >> >Compiled Code)
          >> >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java,
          >Compiled
          >> >Code)
          >> >> ti jan 23 11:12:20 GMT+01:00 2001:<I> <EJB JAR deployment
          >> >F:\Projects\MolStructureDS\MolStructureDS.jar> Transaction:
          >> >'980237619834_1326' rolled back
          >> >> due to EJB exception:
          >> >> javax.ejb.EJBException
          >> >> at
          >>
          >>net.astrazeneca.cmi.data.dataservice.MolStructureDS.register(MolStructureDS
          >..
          >> >java, Compiled Code)
          >> >>
          >> >> Anybody got an idea ? at
          >>
          >>net.astrazeneca.cmi.data.dataservice.MolStructureDSEOImpl.register(MolStruc
          >t
          >> >ureDSEOImpl.java, Compiled Code)
          >> >> at
          >>
          >>net.astrazeneca.cmi.data.dataservice.MolStructureDSEOImpl_WLSkel.invoke(Mol
          >S
          >> >tructureDSEOImpl_WLSkel.java, Compiled Code)
          >> >> at
          >>
          >>weblogic.rmi.extensions.BasicServerObjectAdapter.invoke(BasicServerObjectAd
          >a
          >> >pter.java, Compiled Code)
          >> >> at
          >>
          >>weblogic.rmi.extensions.BasicRequestHandler.handleRequest(BasicRequestHandl
          >e
          >> >r.java, Compiled Code)
          >> >> at
          >>
          >>weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java,
          >> >Compiled Code)
          >> >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java,
          >Compiled
          >> >Code)
          >> >>
          >> >> ti jan 23 11:12:20 GMT+01:00 2001:<E> <Adapter> Exception thrown by
          >rmi
          >> >server:
          >> >[-3565031217135527434S157.96.215.53:[7001,7001,7002,7002,7001,-1]/466]
          >> >>
          >> >> javax.ejb.EJBException
          >> >> at
          >>
          >>net.astrazeneca.cmi.data.dataservice.MolStructureDS.register(MolStructureDS
          >..
          >> >java, Compiled Code)
          >> >> at
          >>
          >>net.astrazeneca.cmi.data.dataservice.MolStructureDSEOImpl.register(MolStruc
          >t
          >> >ureDSEOImpl.java, Compiled Code)
          >> >> at
          >>
          >>net.astrazeneca.cmi.data.dataservice.MolStructureDSEOImpl_WLSkel.invoke(Mol
          >S
          >> >tructureDSEOImpl_WLSkel.java, Compiled Code)
          >> >> at
          >>
          >>weblogic.rmi.extensions.BasicServerObjectAdapter.invoke(BasicServerObjectAd
          >a
          >> >pter.java, Compiled Code)
          >> >> at
          >>
          >>weblogic.rmi.extensions.BasicRequestHandler.handleRequest(BasicRequestHandl
          >e
          >> >r.java, Compiled Code)
          >> >> at
          >>
          >>weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java,
          >> >Compiled Code)
          >> >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java,
          >Compiled
          >> >Code)
          >> >>
          >> >>
          >> >>
          >> >> No matter what I have tried so far the two inserts that are OK are
          >> >commited in Oracle. What I want is to make all three inserts in the
          >> >transaction rolled back.
          >> >>
          >> >> Anybody got an idea ?
          >> >
          >> >
          >>
          >
          >

Rolling back from OIM version 11g to 9.1.0.2

Experts,
OIM version upgrade from 9.1.0.2 to 11g(11.1.1.5) need to be rolled back due to some error.
Just wanted to know views of experts.
Following steps have been completed so far of the upgrade guide [http://docs.oracle.com/cd/E21764_01/upgrade.1111/e10129/upgrade_oim.htm].
•Task 1: Identify and Prepare Oracle Database for Oracle Identity Manager 11g (Optional)
•Task 2: Use the Repository Creation Utility to Create the Schema in the Database
•Task 3: Install Oracle Fusion Middleware
•Task 4: Use Upgrade Assistant to Upgrade the Oracle Identity Manager Schema
•Task 5: Create a WebLogic Domain for Oracle Identity Manager
•Task 6: Start the WebLogic Administration Server
•Task 7: Configure Oracle Identity Manager Server 11g
•Task 8: Configure Node Manager to Start Managed Servers
•Task 9: Start the SOA Managed Server
•Task 10: Start the Oracle Identity Manager Managed Server
•Task 11: Stop the Oracle Identity Manager Managed Server
Rollback strategy:-
1. Delete extra schemas(SOA MDC etc) created during Task2
2. Restoring the OIM DB schema (of version 9.1.0.2) from backup.
3. Updating back path and variables environment with old values
4. Starting the weblogic and OIM application from old Middleware_home and OIM_HOME.
Experts,
Above rollback strategy would be enough or should i take some other point in consideration.
If you can think of any other thing please share..
Thanks,
Manohar

Yes your strategies seems fine. for dropping schema you can RCU as well.
for restore, Drop all the entities manually from oim db schema So you don't have any grant issue while importing old 10g dump
--nayan

Roll back exceptions

We just started getting this error message today, and we have not been able to
reasonable decipher it. I hope someone can help....
Wed Dec 11 13:51:12 EST 2002:<I> <EJB JAR deployment ./myserver5/CORE/IncentiveProgramManager.jar>
Transaction: '1039632533713_4121' rolled back due to EJB exception:
java.lang.NoSuchMethodError: weblogic.ejb.internal.EJBHomeImpl: method setupTransaction(Ljavax/transaction/Transaction;Lweblogic/ejb/internal/MethodInfo;)V
not found
at com.gmac.incentive.IncentiveProgram.IncentiveProgramBeanHomeImpl.preFinderInvoke(IncentiveProgramBeanHomeImpl.java:193)
at com.gmac.incentive.IncentiveProgram.IncentiveProgramBeanHomeImpl.findByPrimaryKey(IncentiveProgramBeanHomeImpl.java:69)
at com.gmac.incentive.IncentiveProgram.IncentiveProgramBeanHomeImpl_ServiceStub.findByPrimaryKey(Compiled
Code)
at com.gmac.incentive.IncentiveProgramManagerEJB.IncentiveProgramManagerBean.updateIncentiveProgram(IncentiveProgramManagerBean.java:1076)
at com.gmac.incentive.IncentiveProgramManagerEJB.IncentiveProgramManagerBeanEOImpl.updateIncentiveProgram(IncentiveProgramManagerBeanEOImpl.java:158)
at com.gmac.incentive.IncentiveProgramManagerEJB.IncentiveProgramManagerBeanEOImpl_ServiceStub.updateIncentiveProgram(Compiled
Code)
at EditIncentiveProgram.service(EditIncentiveProgram.java:472)
at javax.servlet.http.HttpServlet.service(Compiled Code)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(Compiled Code)
at weblogic.servlet.internal.ServletContextImpl.invokeServlet(Compiled
Code)
at weblogic.servlet.internal.ServletContextImpl.invokeServlet(Compiled
Code)
at weblogic.servlet.internal.ServletContextManager.invokeServlet(Compiled
Code)
at weblogic.socket.MuxableSocketHTTP.invokeServlet(Compiled Code)
at weblogic.socket.MuxableSocketHTTP.execute(Compiled Code)
at weblogic.kernel.ExecuteThread.run(Compiled Code)
Wed Dec 11 13:51:12 EST 2002:<E> <ServletContext-General> Servlet failed with
Exception
java.rmi.RemoteException: java.lang.NoSuchMethodError: weblogic.ejb.internal.EJBHomeImpl:
method setupTransaction(Ljavax/transaction/Transaction;Lweblogic/ejb/internal/MethodInfo;)V
not found
at com.gmac.incentive.IncentiveProgram.IncentiveProgramBeanHomeImpl.preFinderInvoke(IncentiveProgramBeanHomeImpl.java:193)
at com.gmac.incentive.IncentiveProgram.IncentiveProgramBeanHomeImpl.findByPrimaryKey(IncentiveProgramBeanHomeImpl.java:69)
at com.gmac.incentive.IncentiveProgram.IncentiveProgramBeanHomeImpl_ServiceStub.findByPrimaryKey(Compiled
Code)
at com.gmac.incentive.IncentiveProgramManagerEJB.IncentiveProgramManagerBean.updateIncentiveProgram(IncentiveProgramManagerBean.java:1076)
at com.gmac.incentive.IncentiveProgramManagerEJB.IncentiveProgramManagerBeanEOImpl.updateIncentiveProgram(IncentiveProgramManagerBeanEOImpl.java:158)
at com.gmac.incentive.IncentiveProgramManagerEJB.IncentiveProgramManagerBeanEOImpl_ServiceStub.updateIncentiveProgram(Compiled
Code)
at EditIncentiveProgram.service(EditIncentiveProgram.java:472)
at javax.servlet.http.HttpServlet.service(Compiled Code)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(Compiled Code)
at weblogic.servlet.internal.ServletContextImpl.invokeServlet(Compiled
Code)
at weblogic.servlet.internal.ServletContextImpl.invokeServlet(Compiled
Code)
at weblogic.servlet.internal.ServletContextManager.invokeServlet(Compiled
Code)
at weblogic.socket.MuxableSocketHTTP.invokeServlet(Compiled Code)
at weblogic.socket.MuxableSocketHTTP.execute(Compiled Code)
at weblogic.kernel.ExecuteThread.run(Compiled Code)
; nested exception is:
java.lang.NoSuchMethodError: weblogic.ejb.internal.EJBHomeImpl: method
setupTransaction(Ljavax/transaction/Transaction;Lweblogic/ejb/internal/MethodInfo;)V
not found
java.lang.NoSuchMethodError: weblogic.ejb.internal.EJBHomeImpl: method setupTransaction(Ljavax/transaction/Transaction;Lweblogic/ejb/internal/MethodInfo;)V
not found
at com.gmac.incentive.IncentiveProgram.IncentiveProgramBeanHomeImpl.preFinderInvoke(IncentiveProgramBeanHomeImpl.java:193)
at com.gmac.incentive.IncentiveProgram.IncentiveProgramBeanHomeImpl.findByPrimaryKey(IncentiveProgramBeanHomeImpl.java:69)
at com.gmac.incentive.IncentiveProgram.IncentiveProgramBeanHomeImpl_ServiceStub.findByPrimaryKey(Compiled
Code)
at com.gmac.incentive.IncentiveProgramManagerEJB.IncentiveProgramManagerBean.updateIncentiveProgram(IncentiveProgramManagerBean.java:1076)
at com.gmac.incentive.IncentiveProgramManagerEJB.IncentiveProgramManagerBeanEOImpl.updateIncentiveProgram(IncentiveProgramManagerBeanEOImpl.java:158)
at com.gmac.incentive.IncentiveProgramManagerEJB.IncentiveProgramManagerBeanEOImpl_ServiceStub.updateIncentiveProgram(Compiled
Code)
at EditIncentiveProgram.service(EditIncentiveProgram.java:472)
at javax.servlet.http.HttpServlet.service(Compiled Code)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(Compiled Code)
at weblogic.servlet.internal.ServletContextImpl.invokeServlet(Compiled
Code)
at weblogic.servlet.internal.ServletContextImpl.invokeServlet(Compiled
Code)
at weblogic.servlet.internal.ServletContextManager.invokeServlet(Compiled
Code)
at weblogic.socket.MuxableSocketHTTP.invokeServlet(Compiled Code)
at weblogic.socket.MuxableSocketHTTP.execute(Compiled Code)
at weblogic.kernel.ExecuteThread.run(Compiled Code)
Any help would be much appreciated.
Jim

Looks like a classpath mismatch between the version of ejbc used to
compile the bean and the server which deployed it.
You must be using 5.1. Newer versions of the server handle this much
better.
-- Rob
Jim Smith wrote:
We just started getting this error message today, and we have not been able to
reasonable decipher it. I hope someone can help....
Wed Dec 11 13:51:12 EST 2002:<I> <EJB JAR deployment ./myserver5/CORE/IncentiveProgramManager.jar>
Transaction: '1039632533713_4121' rolled back due to EJB exception:
java.lang.NoSuchMethodError: weblogic.ejb.internal.EJBHomeImpl: method setupTransaction(Ljavax/transaction/Transaction;Lweblogic/ejb/internal/MethodInfo;)V
not found
at com.gmac.incentive.IncentiveProgram.IncentiveProgramBeanHomeImpl.preFinderInvoke(IncentiveProgramBeanHomeImpl.java:193)
at com.gmac.incentive.IncentiveProgram.IncentiveProgramBeanHomeImpl.findByPrimaryKey(IncentiveProgramBeanHomeImpl.java:69)
at com.gmac.incentive.IncentiveProgram.IncentiveProgramBeanHomeImpl_ServiceStub.findByPrimaryKey(Compiled
Code)
at com.gmac.incentive.IncentiveProgramManagerEJB.IncentiveProgramManagerBean.updateIncentiveProgram(IncentiveProgramManagerBean.java:1076)
at com.gmac.incentive.IncentiveProgramManagerEJB.IncentiveProgramManagerBeanEOImpl.updateIncentiveProgram(IncentiveProgramManagerBeanEOImpl.java:158)
at com.gmac.incentive.IncentiveProgramManagerEJB.IncentiveProgramManagerBeanEOImpl_ServiceStub.updateIncentiveProgram(Compiled
Code)
at EditIncentiveProgram.service(EditIncentiveProgram.java:472)
at javax.servlet.http.HttpServlet.service(Compiled Code)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(Compiled Code)
at weblogic.servlet.internal.ServletContextImpl.invokeServlet(Compiled
Code)
at weblogic.servlet.internal.ServletContextImpl.invokeServlet(Compiled
Code)
at weblogic.servlet.internal.ServletContextManager.invokeServlet(Compiled
Code)
at weblogic.socket.MuxableSocketHTTP.invokeServlet(Compiled Code)
at weblogic.socket.MuxableSocketHTTP.execute(Compiled Code)
at weblogic.kernel.ExecuteThread.run(Compiled Code)
Wed Dec 11 13:51:12 EST 2002:<E> <ServletContext-General> Servlet failed with
Exception
java.rmi.RemoteException: java.lang.NoSuchMethodError: weblogic.ejb.internal.EJBHomeImpl:
method setupTransaction(Ljavax/transaction/Transaction;Lweblogic/ejb/internal/MethodInfo;)V
not found
at com.gmac.incentive.IncentiveProgram.IncentiveProgramBeanHomeImpl.preFinderInvoke(IncentiveProgramBeanHomeImpl.java:193)
at com.gmac.incentive.IncentiveProgram.IncentiveProgramBeanHomeImpl.findByPrimaryKey(IncentiveProgramBeanHomeImpl.java:69)
at com.gmac.incentive.IncentiveProgram.IncentiveProgramBeanHomeImpl_ServiceStub.findByPrimaryKey(Compiled
Code)
at com.gmac.incentive.IncentiveProgramManagerEJB.IncentiveProgramManagerBean.updateIncentiveProgram(IncentiveProgramManagerBean.java:1076)
at com.gmac.incentive.IncentiveProgramManagerEJB.IncentiveProgramManagerBeanEOImpl.updateIncentiveProgram(IncentiveProgramManagerBeanEOImpl.java:158)
at com.gmac.incentive.IncentiveProgramManagerEJB.IncentiveProgramManagerBeanEOImpl_ServiceStub.updateIncentiveProgram(Compiled
Code)
at EditIncentiveProgram.service(EditIncentiveProgram.java:472)
at javax.servlet.http.HttpServlet.service(Compiled Code)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(Compiled Code)
at weblogic.servlet.internal.ServletContextImpl.invokeServlet(Compiled
Code)
at weblogic.servlet.internal.ServletContextImpl.invokeServlet(Compiled
Code)
at weblogic.servlet.internal.ServletContextManager.invokeServlet(Compiled
Code)
at weblogic.socket.MuxableSocketHTTP.invokeServlet(Compiled Code)
at weblogic.socket.MuxableSocketHTTP.execute(Compiled Code)
at weblogic.kernel.ExecuteThread.run(Compiled Code)
; nested exception is:
java.lang.NoSuchMethodError: weblogic.ejb.internal.EJBHomeImpl: method
setupTransaction(Ljavax/transaction/Transaction;Lweblogic/ejb/internal/MethodInfo;)V
not found
java.lang.NoSuchMethodError: weblogic.ejb.internal.EJBHomeImpl: method setupTransaction(Ljavax/transaction/Transaction;Lweblogic/ejb/internal/MethodInfo;)V
not found
at com.gmac.incentive.IncentiveProgram.IncentiveProgramBeanHomeImpl.preFinderInvoke(IncentiveProgramBeanHomeImpl.java:193)
at com.gmac.incentive.IncentiveProgram.IncentiveProgramBeanHomeImpl.findByPrimaryKey(IncentiveProgramBeanHomeImpl.java:69)
at com.gmac.incentive.IncentiveProgram.IncentiveProgramBeanHomeImpl_ServiceStub.findByPrimaryKey(Compiled
Code)
at com.gmac.incentive.IncentiveProgramManagerEJB.IncentiveProgramManagerBean.updateIncentiveProgram(IncentiveProgramManagerBean.java:1076)
at com.gmac.incentive.IncentiveProgramManagerEJB.IncentiveProgramManagerBeanEOImpl.updateIncentiveProgram(IncentiveProgramManagerBeanEOImpl.java:158)
at com.gmac.incentive.IncentiveProgramManagerEJB.IncentiveProgramManagerBeanEOImpl_ServiceStub.updateIncentiveProgram(Compiled
Code)
at EditIncentiveProgram.service(EditIncentiveProgram.java:472)
at javax.servlet.http.HttpServlet.service(Compiled Code)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(Compiled Code)
at weblogic.servlet.internal.ServletContextImpl.invokeServlet(Compiled
Code)
at weblogic.servlet.internal.ServletContextImpl.invokeServlet(Compiled
Code)
at weblogic.servlet.internal.ServletContextManager.invokeServlet(Compiled
Code)
at weblogic.socket.MuxableSocketHTTP.invokeServlet(Compiled Code)
at weblogic.socket.MuxableSocketHTTP.execute(Compiled Code)
at weblogic.kernel.ExecuteThread.run(Compiled Code)
Any help would be much appreciated.
Jim

Rolled back JTA TX marked active/inflight

          Hello. I am writing a message driven bean that utilizes container managed transaction
          demarcation for the onMessage method (letting the container worry about msg acknowledgement).
          The MDB relays message information to a legacy system. If the legacy system is
          down, I want to retry message delivery at a later point, so I mark the current
          transaction as rolled back (via the setRollbackOnly() method in my MessageDrivenContext).
          This causes the EJB container to continually call onMessage() with my message
          beans, creating a large amount of rolled back exceptions. These rolled back transactions,
          however, are marked as active/inflight by the WLS transaction manager, leading
          to resource starvation and inability to create transactions because of an overflow
          of the "Active Transaction" watermark (configurable in mydomain->JTA->Active Transactions),
          although the JTA monitoring tools clearly indicate that the TX has been rolled
          back.
          Eventually these "rolled back exceptions" are purged from the Inflight Transaction
          list, and I can once again create transactions. Any ideas on how to fix this/workarounds/bugfixes?
          Please cc: me if you respond as well
          Thanks,
          Alex
          ---- snippets follow ----
          Here is a snippet from the mydomain->myserver->Monitoring->JTA->Inflight Transactions
          page
          Name Status Servers Resources Properties
          (key=value)
          (none) Rolled back. [Reason = weblogic.transaction.internal.AppSetRollbackOnlyException]
          alexd {JMS_jmsStoreTest=rolledback} (none)
          And a listing of the JTA monitoring info
          Total Transactions: 45060
          Total Committed: 131
          Total Rolled Back: 44929
          Timeout Rollbacks: 0
          Resource Rollbacks: 0
          Application Rollbacks: 44929


I know this is fixed in WLS 6.1's GA release. Basically, the problem is
          that the EJB container is marking the transaction for rollback where it
          should be rolling it back. That's why you have so many tx's in-flight.
          They are waiting to time-out.
          -- Rob
          Alex DeNeui wrote:
          >
          > Hello. I am writing a message driven bean that utilizes container managed transaction
          > demarcation for the onMessage method (letting the container worry about msg acknowledgement).
          >
          > The MDB relays message information to a legacy system. If the legacy system is
          > down, I want to retry message delivery at a later point, so I mark the current
          > transaction as rolled back (via the setRollbackOnly() method in my MessageDrivenContext).
          > This causes the EJB container to continually call onMessage() with my message
          > beans, creating a large amount of rolled back exceptions. These rolled back transactions,
          > however, are marked as active/inflight by the WLS transaction manager, leading
          > to resource starvation and inability to create transactions because of an overflow
          > of the "Active Transaction" watermark (configurable in mydomain->JTA->Active Transactions),
          > although the JTA monitoring tools clearly indicate that the TX has been rolled
          > back.
          >
          > Eventually these "rolled back exceptions" are purged from the Inflight Transaction
          > list, and I can once again create transactions. Any ideas on how to fix this/workarounds/bugfixes?
          >
          > Please cc: me if you respond as well
          >
          > Thanks,
          > Alex
          >
          > ---- snippets follow ----
          >
          > Here is a snippet from the mydomain->myserver->Monitoring->JTA->Inflight Transactions
          > page
          > -----------------
          > Name Status Servers Resources Properties
          > (key=value)
          > (none) Rolled back. [Reason = weblogic.transaction.internal.AppSetRollbackOnlyException]
          > alexd {JMS_jmsStoreTest=rolledback} (none)
          > -----------------
          >
          > And a listing of the JTA monitoring info
          > -----------------
          > Total Transactions: 45060
          > Total Committed: 131
          > Total Rolled Back: 44929
          > Timeout Rollbacks: 0
          > Resource Rollbacks: 0
          > Application Rollbacks: 44929
          > ------------------
          Coming Soon: Building J2EE Applications & BEA WebLogic Server
          by Michael Girdley, Rob Woollen, and Sandra Emerson
          http://learnweblogic.com

Rolling back of Quick Pay Pre-payment and Quick Pay in case of void cheque

Hi All
I am facing an issue if you can help me out of if
Here is a scenario
a payroll manager runs the following processes.
1. Payroll run
2. Pre-Payments
3. Payroll Archiver
4. Payment Output file
After running all these process payroll manager finds that he also has to make an adhoc payment on account of car loan of AED 150,000.
So he runs following processes
1. Quick pay for Car loan
2. Quick pay pre-payments (payment made through check)
3. payroll archiver
4. Cheque Writer.
Now due to some technical fault, alignment on printing of cheque becomes disturbed there for cheque misprinted.
Payroll manager runs Void Cheque process to cancel the cheque.
After all these processes which has run successfully, order comes from upper management to rollback quickpay for adhoc payment of loan.
Now question is how it can be achieved.
I tried different things as follows
On Assignment Process results screen i queried the assignment which all the processes in descending order.
I tried to start roll back from cheque writer but system didn't allowed to do this because of check Void process.
I tried to start rollback from Magnetic report, system allowed to roll it back.
Then i tried to rollback Quick-pay prepayment, system did not allow me be do it. There fore i couldn't run rollback for Quick-pay.
There is an another thing i tried.
On "Assignment Process Result" screen i queried assignment. Then i delete the first entry of Void cheque by using delete option from menu bar on top and saved the record. then i delete cheque writer entry and saved the record. Then i run rollback for quick pay pre-payments and ran it successfully and then lastly i ran rollback for quick pay run.
One thing cautioned me that if I delete the void cheque entry then its history may be lost or have lost and on the other hand with out deleting void cheque i cannot proceed to rollback quick pay.
Kindly tell me the best way to run rollback for quick pay in this situation.
Regards
Majid

Bt do not provide broadband only so you need existing account holder to add broadband to phone account and then you can pay back the account holder - probably not what you want
the 12 months advance applies to the line rental not the broadband - as I said BT do not sell broadband only you buy a package which includes phone
If you like a post, or want to say thanks for a helpful answer, please click on the Ratings star on the left-hand side of the post.
If someone answers your question correctly please let other members know by clicking on ’Mark as Accepted Solution’.

How do I roll-back to the previous version of Firefox? An auto update occurred and now one of the programs used at the office (ACT! v6.0 SwiftMail) won't run with the browser.

The office I work in uses a very old version of ACT!, an accounting package. This package has a component called SwiftPage, an antiquated email system that enables us to email from the ACT DB. SwiftPage runs via the web browser.
Firefox just did an auto update (that I will have to find out how to turn off) and now SwiftPage won't run as it is not compatible.
Can I "roll-back" my version of Firefox or do I have to uninstall and try to re-install an older version?
HELP!

Try loading and using the add-on from this link: https://addons.mozilla.org/en-US/firefox/addon/add-on-compatibility-reporter/
Many add-ons do in fact work if you force them to run. The procedure to roll-back is given in this article: [[installing previous versions of firefox]]
Unfortunately the official Firefox policy is that you downgrade to 3.6 which is supported for a while longer, and not the now unsupported Firefox 4. If after installing and running the ''add-on compatibility reporter'' you still have problems there are ways around the official policy.
I think it is absurd that Firefox 4 may be used by tens of millions of users one day and a few days later those that upgrade to Firefox 5 should be not only told not to use a now unsupported browser, if they need to revert due to problems, but are actually obstructed in attempts to do so. See also [/questions/840397#answer-205154]

Regarding DB adapter transactions roll back

Hi All,
In a BPEL, using while loop i'm trying to insert records in a table(business table-Oracle XE DB). If any errors happen during the insertion, it should rollback the previous insertions happened in the business table and insert the error details in the log table.
Example: Let's say 5 records need to be inserted in business table, after first two records get inserted successfully, due to invalid data, 3rd record fails to get inserted.
Things i have done,
1) I have a catch block to catch the errors
2) I have an invoke activity in the catch block to invoke the DB adapter to insert error details in log table.
3) Throw activity with bpelx:rollback to roll back the previous transactions.
Question: After the error details get inserted in log table, since i have a throw activity with bpelx rollback, all the previous DB transactions including the log table insertion is getting rolled back. I don't want my log table record insertion to be rolled back, only the records which i have already inserted successfully in the business table needs to be rolled back.
Can anyone let me know, how to handle such a situation? your response is greatly appreciated.

You need to ensure that your process is working in a single transaction.
You are correctly using the XA datasource.
Next you need to ensure that you do not have a dehydration point in the process and if there is a call to another BPEL process they are in a same transaction.

Toplink 9.0.4.8 and JTS on OAS 10.1.2.0.0 and 10.1.2.0.2 not rolling back

Re-Posting message with more information.
Toplink 9.0.4.8 and JTS not rolling back transaction
Hi
Scenario:
I have a session bean (EJB1) calling a session bean (EJB2).
When an EJB1 is called, EJB1 persists data on to Table1 in database.
And EJB1 makes multiple calls to EJB2 to create entries in three different tables. Trans-attribute is set as required on both EJBS.
Problem:
EJB1 gets a Runtime Exception while inserting the data into TABLE1 (ORA-12899: value too large for column), EJB1 transaction is rollback, but all other transactions related to EJB2 are getting committed. I assume that they should roll back too.
Also, I did JAD on external transaction controller and listener and noticed that there is a transaction associated to each call. Meaning EJB1 had Transaction T1 and EJB2 had T2, T3, and T4 for the subsequent calls. When EJB1 is getting runtime exception in the method beforeCompletion(), the it calls rollbackGlobalTransaction() which is calling T1.setRollbackonly(). But not on on T2, T3, and T4 rollback
Am I missing anything?
Please help me
Here are my configuration details:
The datasource configuration:
<data-source name="myTxDataSource"
class="com.evermind.sql.OrionCMTDataSource"
location="jdbc/myTxDataSourceCoreDS"
xa-location="jdbc/xa/myTxDataSourceXADS"
ejb-location="jdbc/myTxDataSourceDS"
pooled-location="jdbc/myTxDataSourcePooledDS"
connection-driver="oracle.jdbc.driver.OracleDriver"
username="duser"
password="d123"
url="jdbc:oracle:thin:@localhost:1521:ORCL"
inactivity-timeout="30"
/>
Sessions.xml
<login>
<driver-class>oracle.jdbc.driver.OracleDriver</driver-class>
<connection-url>jdbc:oracle:thin:@localhost:1521:orcl</connection-url>
<datasource>jdbc/DimpleTxDataSourceCoreDS</datasource>
<user-name>duser</user-name>
<encryption-class-name>oracle.toplink.internal.security.JCEEncryptor</encryption-class-name>
<encrypted-password>22F7AFE6F6B9672435537CE1189E123DD62D1A19DF561D1E</encrypted-password>
<uses-native-sequencing>true</uses-native-sequencing>
<uses-external-connection-pool>true</uses-external-connection-pool>
<uses-external-transaction-controller>true</uses-external-transaction-controller>
</login>
<external-transaction-controller-class>oracle.toplink.jts.oracle9i.Oracle9iJTSExternalTransactionController</external-transaction-controller-class>
Toplink Helper class that is used by both EJB's
This one uses SessionBroker. here is how it is initialized:
SessionManager manager = SessionManager.getManager();
sessionBroker = (SessionBroker) manager.getSession(xmlLoader,
sessionBrokerName, this.getClass().getClassLoader());
Oracle9iJTSExternalTransactionController extController = new Oracle9iJTSExternalTransactionController();
sessionBroker.setExternalTransactionController(extController);
It has common following commong methods:
public UnitOfWork getUnitOfWork() {
UnitOfWork uow = sessionBroker.getActiveUnitOfWork();
return uow;
public Object create(Object o)
UnitOfWork uow = getUnitOfWork();
uow.registerNewObject(o);
// added so that the assigned sequence number will be available before the commit happens
uow.assignSequenceNumber(o);
return o;
}

A couple of this appear different in your sessions.xml. To do what you want you need to configure TopLink to:
1. Use an external XT controller - requires flag to be set and controller provided
2. Use the OC4J data source - requires flag to be set and data source name provided
I notice that your sessions.xml has both a data source name as well as a direct connection URL.
Here is a sample that shows the proper settings for the external TX and data source usage:
<?xml version = '1.0' encoding = 'UTF-8'?>
<!DOCTYPE toplink-configuration PUBLIC "-//Oracle Corp.//DTD TopLink Sessions 9.0.4//EN" "sessions_9_0_4.dtd">
<toplink-configuration>
   <session>
      <name>default</name>
      <project-xml>META-INF/tlMap1.xml</project-xml>
      <session-type>
         <server-session/>
      </session-type>
      <login>
         <datasource>jdbc/DimpleTxDataSourceCoreDS</datasource>
         <platform-class>oracle.toplink.platform.database.oracle.Oracle10Platform</platform-class>
         <uses-external-connection-pool>true</uses-external-connection-pool>
         <uses-external-transaction-controller>true</uses-external-transaction-controller>
      </login>
      <external-transaction-controller-class>oracle.toplink.jts.oracle9i.Oracle9iJTSExternalTransactionController</external-transaction-controller-class>
      <enable-logging>true</enable-logging>
      <logging-options>
         <print-thread>false</print-thread>
         <print-date>false</print-date>
      </logging-options>
   </session>
</toplink-configuration>Doug

Toplink 9.0.4.8 and JTS on OAS 10.1.2.0.0 and 10.1.2.0.2 not rolling back t

Toplink 9.0.4.8 and JTS not rolling back transaction
Hi
Scenario:
I have a session bean (EJB1) calling a session bean (EJB2).
When an EJB1 is called, EJB1 persists data on to Table1 in database.
And EJB1 makes multiple calls to EJB2 to create entries in three different tables. Trans-attribute is set as required on both EJBS.
Problem:
EJB1 gets a Runtime Exception while inserting the data into TABLE1 (ORA-12899: value too large for column), EJB1 transaction is rollback, but all other transactions related to EJB2 are getting committed. I assume that they should roll back too.
Also, I did JAD on external transaction controller and listener and noticed that there is a transaction associated to each call. Meaning EJB1 had Transaction T1 and EJB2 had T2, T3, and T4 for the subsequent calls. When EJB1 is getting runtime exception in the method beforeCompletion(), the it calls rollbackGlobalTransaction() which is calling T1.setRollbackonly(). But not on on T2, T3, and T4 rollback
Am I missing anything?
Please help me
Here are my configuration details:
The datasource configuration:
<data-source name="myTxDataSource"
class="com.evermind.sql.OrionCMTDataSource"
location="jdbc/myTxDataSourceCoreDS"
xa-location="jdbc/xa/myTxDataSourceXADS"
ejb-location="jdbc/myTxDataSourceDS"
pooled-location="jdbc/myTxDataSourcePooledDS"
connection-driver="oracle.jdbc.driver.OracleDriver"
username="duser"
password="d123"
url="jdbc:oracle:thin:@localhost:1521:ORCL"
inactivity-timeout="30"
/>
Sessions.xml
<login>
<driver-class>oracle.jdbc.driver.OracleDriver</driver-class>
<connection-url>jdbc:oracle:thin:@localhost:1521:orcl</connection-url>
<datasource>jdbc/DimpleTxDataSourceCoreDS</datasource>
<user-name>duser</user-name>
<encryption-class-name>oracle.toplink.internal.security.JCEEncryptor</encryption-class-name>
<encrypted-password>22F7AFE6F6B9672435537CE1189E123DD62D1A19DF561D1E</encrypted-password>
<uses-native-sequencing>true</uses-native-sequencing>
<uses-external-connection-pool>true</uses-external-connection-pool>
<uses-external-transaction-controller>true</uses-external-transaction-controller>
</login>
<external-transaction-controller-class>oracle.toplink.jts.oracle9i.Oracle9iJTSExternalTransactionController</external-transaction-controller-class>
Toplink Helper class that is used by both EJB's
This one uses SessionBroker. here is how it is initialized:
SessionManager manager = SessionManager.getManager();
sessionBroker = (SessionBroker) manager.getSession(xmlLoader,
sessionBrokerName, this.getClass().getClassLoader());
Oracle9iJTSExternalTransactionController extController = new Oracle9iJTSExternalTransactionController();
sessionBroker.setExternalTransactionController(extController);
It has common following commong methods:
public UnitOfWork getUnitOfWork() {
UnitOfWork uow = sessionBroker.getActiveUnitOfWork();
return uow;
public Object create(Object o)
UnitOfWork uow = getUnitOfWork();
uow.registerNewObject(o);
// added so that the assigned sequence number will be available before the commit happens
uow.assignSequenceNumber(o);
return o;
}

Doug, Andrei and others
I found the problem. I have a Delegate that provides access to all EJBS. This delegate is used by both the webtier and middle tier.It is written in a generic fashion so that the web server and middle tier does not have to be co-located in one container. getInitialContext() which is implemented as follows:
private static Context getInitialContext() throws NamingException
// Get InitialContext for Embedded OC4J.
// The embedded server must be running for lookups to succeed.
// actual code reads from the external parameters
String contextFactory = "com.evermind.server.rmi.RMIInitialContextFactory";
String principal = "admin";
String passwd = "admin123";
String providerURL = "ormi://localhost:3201/shc";
Hashtable env = new Hashtable();
env.put(Context.INITIAL_CONTEXT_FACTORY, contextFactory);
env.put(Context.SECURITY_PRINCIPAL, principal);
env.put(Context.SECURITY_CREDENTIALS, passwd);
env.put(Context.PROVIDER_URL, providerURL);
env.put("dedicated.rmicontext","true");
return new InitialContext(env);
When the EJB1 tries to look up for EJB2, container thinks that the call is from outside the container and it is starting a new transaction.
When I changed the EJB1 to look up EJB2 to get the context as shown below,every thing seems to rolling back.
private static Context getInitialContext() throws NamingException
return new InitialContext();
Thanks again for pointing me in the right direction.
I will post the same message in other threads.
Raju

Transaction rolled back......soa 11g

I have a bpel process 1 which calls bpel process 2. Bpel process 2 is a file write. In my instance bpel process 2 is called and the file is written successfully. but bpel process 1 gets errored out with no errors being displayed. The bpel process 1 has a red colour at the point where it invokes the child process. and also a line saying transaction rolled back.
But there is no error in the child process instance
Please do suggest me the solution.

The issue may be due to the transaction timeout, verify the configured timeouts and the processing time of the process B.
Try increasing Sync Max Time Out and the other timeouts accordingly and test it.
Refer the below URL for the details of configuring the timeouts.
http://www.albinsblog.com/2011/11/oracle-soa-11g-configure-transaction_20.html
Regards
Albin I

Once Again: Transaction is not rolled back...

Hi all,
I'm almost at the end of my project with Toplink. but I have to solve this transaction rollback problem. Here is my previous message. any comment is more than welcome.
The problem is this, I pass 2 objects to Toplink to update in database using activeUnitOfWork.shallowMergeClone() method.
one of the updates fails then I expect everything to be rolled back within the same unitofwork. but NOT. the other object is quite well updated in database even though they are merged in the same unit of work... please HELP...
here is the log :
UnitOfWork(31228)--JTS#beforeCompletion()
UnitOfWork(31228)--#executeQuery(WriteObjectQuery(com.vnu.publitec.axis.persistence.Parameters@7a0b))
UnitOfWork(31228)--Connection(31249)--UPDATE PARAMETERS SET PARAM_VALUE = '26' WHERE (PARAM_NAME = 'TEST_PARAMETER_2')
UnitOfWork(31228)--#reconnecting to external connection pool
UnitOfWork(31228)--#executeQuery(WriteObjectQuery(com.vnu.publitec.axis.persistence.Parameters@7a06))
UnitOfWork(31228)--Connection(31249)--UPDATE PARAMETERS SET PARAM_MAX_SIZE = 666666, PARAM_COMMENTS = 'updated by new axis...', PARAM_VALUE = '18' WHERE (PARAM_NAME = 'TEST_PARAMETER_1')
UnitOfWork(31228)--EXCEPTION [TOPLINK-4002] (TopLink - 9.0.3 (Build 423)): oracle.toplink.exceptions.DatabaseException
EXCEPTION DESCRIPTION: java.sql.SQLException: ORA-01438: value larger than specified precision allows for this column
INTERNAL EXCEPTION: java.sql.SQLException: ORA-01438: value larger than specified precision allows for this column
...... //some more message
UnitOfWork(31228)--JTS#afterCompletion()
UnitOfWork(31228)--release unit of work
ClientSession(31229)--client released
environment information is :
J2EE Server is Oracle9iAS (9.0.3.0.0) Containers for J2EE
and following is a piece of sessions.xml file related to external transaction controller settings :
<session-type>
<server-session/>
</session-type>
<login>
<datasource>java:comp/env/jdbc/xxx</datasource>
<uses-native-sql>true</uses-native-sql>
<uses-external-transaction-controller>true</uses-external-transaction-controller>
<uses-external-connection-pool>true</uses-external-connection-pool>
</login>
<external-transaction-controller-class>oracle.toplink.jts.oracle9i.Oracle9iJTSExternalTransactionController</external-transaction-controller-class>
thanks
Erdem.

Hi James,
As Erdem is not available, I am now taking care of the issue. The datasource name in session.xml refers to the one defined in OC4J data-sources.xml "ejb-location" attribute of "data-source" element. Below, I attach the relevant sections of both files
session.xml
<session>
<name>Axis_session</name>
<project-xml>AxisCDM.xml</project-xml>
<session-type>
<server-session/>
</session-type>
<login>
<datasource>java:comp/env/jdbc/AXIS_323DS</datasource>
<uses-native-sql>true</uses-native-sql>
<uses-external-transaction-controller>true</uses-external-transaction-controller>
<uses-external-connection-pool>true</uses-external-connection-pool>
</login>
<external-transaction-controller-class>oracle.toplink.jts.oracle9i.Oracle9iJTSExternalTransactionController</external-transaction-controller-class>
data-sources.xml:
<data-source
class="com.evermind.sql.DriverManagerDataSource"
name="AXIS_323DS"
location="jdbc/AXIS_323CoreDS"
xa-location="jdbc/xa/AXIS_323XADS"
ejb-location="jdbc/AXIS_323DS"
connection-driver="oracle.jdbc.driver.OracleDriver"
username="XXX"
password="XXX"
url="jdbc:oracle:oci8:@ddb"
inactivity-timeout="30"
connection-retry-interval="1"
/>
On the client we get the following exception:
com.evermind.server.rmi.OrionRemoteException: Transaction was rolled back: Error in transaction: EXCEPTION [TOPLINK-4002] (TopLink - 9.0.3 (Build 423)): oracle.toplink.exceptions.DatabaseException
EXCEPTION DESCRIPTION: java.sql.SQLException: ORA-01438: value larger than specified precision allows for this column
On the server, we have implemented SessionSynchronization to monitor the transaction. afterCompletion method gets a boolean value "true" indicating that the transaction was comitted.
Any database operation that was successful before the erroneous case was saved in DB.
Thanks,
Melih

Transaction is not Rolling Back in Stateless Session Bean

          Hi,
          I am using UserTransaction in Stateless Session bean .
          Transaction is not rolling back.
          The following code is writen in stateless session bean. In UserTransaction i am
          calling Two methods of another stateless session bean.
          The problem is if doJob2() method fails, doJob1() method is rolling back. These
          two methods consist of SQL statement with different Connection Object from TXDataSource.And
          session bean(TestSession) is set to CMT, attribute as "Required".
          try{
          Context ictx=new InitialContext();
          TestHome home=(TestHome)ictx.lookup("TestSession");
               utx = sessionCtx.getUserTransaction();
               utx.begin();
          TestRemote remote=home.create();
               remote.doJob1();
               remote.doJob2();
               utx.commit();
          }catch(Exception e)
               try{
               utx.rollback();
          }catch(Exception ex)
               System.out.println("unable to rollback"+ex);
          if any SQL Exception as occured in doJob2(), its calling method utx.rollback()
          in catch block. but SQL statements executed thru. doJob1() are not rolling back.
          what might be the reason?
          thanks
          Ranganath


          Thanx Priscilla ,
          Transaction is working.
          ranganath
          "Priscilla Fung" <[email protected]> wrote:
          >
          >In your ejb-jar.xml, you should specify <transaction-type> element to
          >be "Container"
          >for container-managed transaction. If you specified it to be "Bean" for
          >bean-managed
          >transaction, EJB ontainer will suspend the caller's transaction before
          >starting
          >a new transaction for your doJobX() methods. Thus, doJob1()nd doJob2()
          >will be
          >executing in different transactions, and thus rolling back doJob2()'s
          >transaction
          >will have no effect on work done and committed in doJob1()'s transaction.
          >
          >Regards,
          >
          >Priscilla
          >
          >
          >"Ranganath" <[email protected]> wrote:
          >>
          >>
          >>
          >>I am sending config.xml,deployment descriptors, code snippet for TestSession.
          >>i
          >>am using weblogic6.0sp2.
          >>if you need any aditional info. please let me know.
          >>
          >>thanks
          >>ranganath
          >>
          >>EJB-JAR.xml
          >>
          >><?xml version="1.0"?>
          >>
          >><!DOCTYPE ejb-jar PUBLIC '-//Sun Microsystems, Inc.//DTD Enterprise
          >JavaBeans
          >>1.1//EN' 'http://java.sun.com/j2ee/dtds/ejb-jar_1_1.dtd'>
          >>
          >><ejb-jar>
          >>     <enterprise-beans>
          >>     <session>
          >>          <ejb-name>TestSession</ejb-name>
          >>          <home>com.apar.sslbridge.test.TestHome</home>
          >>          <remote>com.apar.sslbridge.test.TestRemote</remote>
          >>          <ejb-class>com.apar.sslbridge.test.TestBean</ejb-class>
          >>          <session-type>Stateless</session-type>
          >>          <transaction-type>Bean</transaction-type>
          >>          <resource-ref>
          >>     <res-ref-name>jdbc/oraclePool</res-ref-name>
          >>     <res-type>javax.sql.DataSource</res-type>
          >>     <res-auth>Container</res-auth>
          >>          </resource-ref>
          >>     </session>
          >>     </enterprise-beans>
          >>     <assembly-descriptor>
          >>     <container-transaction>
          >>          <method>
          >>          <ejb-name>TestSession</ejb-name>
          >>          <method-intf>Remote</method-intf>
          >>          <method-name>*</method-name>
          >>          </method>
          >>          <trans-attribute>Required</trans-attribute>
          >>     </container-transaction>
          >> </assembly-descriptor>
          >></ejb-jar>
          >>
          >>
          >>TestSession CODE:
          >>
          >>
          >>     public void doJob1() throws RemoteException
          >>     {
          >>     Statement st = null;
          >>     String query=null;
          >>     try{
          >>     con=getConnection();
          >>     st=con.createStatement();
          >>     query="insert into x values("+x+++")";
          >>     System.out.println(query);
          >>     int rec=st.executeUpdate(query);
          >>     }catch(SQLException sqle)
          >>     {
          >>     System.out.println("SQL Exception "+sqle);
          >> throw new RemoteException("RemoteException*****SQLError");
          >>     } catch (Exception e) {
          >>     System.out.println("Exception "+e);
          >> throw new RemoteException("RemoteException*****GenralError");
          >> }
          >>}
          >>
          >>
          >> public void doJob2()throws RemoteException
          >> {
          >> Connection con=null;
          >> Statement st = null;
          >> String query=null;
          >> try{
          >> con=getConnection();
          >> st=con.createStatement();
          >> query="insert into y values("+x+++")";
          >> System.out.println(query);
          >> int rec=st.executeUpdate(query);
          >> }catch(SQLException sqle)
          >> {
          >> System.out.println("SQL Exception "+sqle);
          >> throw new RemoteException("RemoteException*****SQLError");
          >> } catch (Exception e) {
          >> System.out.println("Exception "+e);
          >> throw new RemoteException("RemoteException*****GenralError");
          >>}
          >>}
          >>private Connection getConnection(){
          >>try {
          >>Connection con = StaticParams.POOL_DATASOURCE.getConnection();
          >>return con;
          >>     } catch(Exception e) {
          >>     System.out.println("TestBean.getConnection() Unable to get get pool
          >>connection
          >>" + e);
          >>     }
          >>}
          >>
          >>
          >>
          >>
          >>"Priscilla Fung" <[email protected]> wrote:
          >>>
          >>>It should work if you are using TxDataSource. Could you post your
          >config.xml,
          >>>deployment descriptors, code snippet for TestSession?
          >>>
          >>>Regards,
          >>>
          >>>Priscilla
          >>>
          >>>"Ranganath" <[email protected]> wrote:
          >>>>
          >>>>Hi,
          >>>>
          >>>> I am using UserTransaction in Stateless Session bean .
          >>>> Transaction is not rolling back.
          >>>>
          >>>>The following code is writen in stateless session bean. In UserTransaction
          >>>>i am
          >>>>calling Two methods of another stateless session bean.
          >>>> The problem is if doJob2() method fails, doJob1() method is rolling
          >>>> back. These
          >>>>two methods consist of SQL statement with different Connection Object
          >>>>from TXDataSource.And
          >>>>session bean(TestSession) is set to CMT, attribute as "Required".
          >>>>
          >>>> try{
          >>>> Context ictx=new InitialContext();
          >>>> TestHome home=(TestHome)ictx.lookup("TestSession");
          >>>>     utx = sessionCtx.getUserTransaction();
          >>>>     utx.begin();
          >>>> TestRemote remote=home.create();
          >>>>     remote.doJob1();
          >>>>     remote.doJob2();
          >>>>     utx.commit();
          >>>> }catch(Exception e)
          >>>> {
          >>>>     try{
          >>>>      utx.rollback();
          >>>> }catch(Exception ex)
          >>>> {
          >>>>     System.out.println("unable to rollback"+ex);
          >>>>     }
          >>>> }
          >>>>if any SQL Exception as occured in doJob2(), its calling method utx.rollback()
          >>>>in catch block. but SQL statements executed thru. doJob1() are not
          >>rolling
          >>>>back.
          >>>>what might be the reason?
          >>>>
          >>>>thanks
          >>>>Ranganath
          >>>
          >>
          >

Websphere 5.0 & JDBC : LocalTransaction rolled-back due to setRollbackOnly.

Similar Messages

Maybe you are looking for