Ejb3 isolated (autonomus) transaction/commit

I'm using XA (2-phase) transaction. I want to log to one log-table through Log class and Entity Manager. My method inside EJB Session bean looks like:
private void logError(Throwable throwable) {
    LogEntity logEntity = new LogEntity();
    // Set everything
    entityManager.persist(logEntity);
    entityManager.flush();
}I want to it in isolated (autonomous) transaction independent of any "outer" transaction. I have already tried to add @TransactionAttribute(value = TransactionAttributeType.REQUIRES_NEW) and @TransactionAttribute(value = TransactionAttributeType.NOT_SUPPORTED) before method name and does not work.
Before I call EJB3 method I create user transaction like:
try {
    UserTransaction transaction = (UserTransaction)context.lookup("javax.transaction.UserTransaction");
    transaction.begin();
    // Call EJB3 method
    transaction.commit();
} catch (Throwable t) {
    t.printStackTrace();
    try {
        transaction.rollback();
    } catch (SystemException e) {
        e.printStackTrace();
}I want to Log no matter if commit is done or rollback is done or none. How to? I have already tried to add annotation TransactionAttribute like TransactionAttributeType.NOT_SUPPORTED. Also tried al other values for TransactionAttribute, but without luck.
Regards

{forum:id=972} seems like a better place for your question

Similar Messages

  • Commit in sp  having  globle table and function with autonomus transaction

    hi gurus,
    1)  i want to know if we populate a globle table in sp  then give  commit  then weather data will be present in globle table or not ..?
    globle table :-
    ON COMMIT delete  ROWS
    NOCACHE;
    2)  in same sp if we call a function having  autonomus transaction  and commit  then wath will happen ..

    1) i want to know if we populate a globle table in sp then give commit then weather data will be present in globle table or not ..?
    globle table :-
    ON COMMIT delete ROWS
    NOCACHE;Data will be deleted from the Global Temporary Table.
    2) in same sp if we call a function having autonomus transaction and commit then wath will happen ..Data Will not be deleted from the Global Temporary Table.

  • Transaction commit unsuccessfully - during import of Profit center in 8.81

    Hello Experts!
    Good day! I've been trying to upload using DTW template for cost center.  During "run simulation" it was run successfully, but during actual import, the error per line is transaction commit unsuccessfully.  I have tried several date format but the only format accepted is yyyy-mm-dd.  I cannot figure out the reason for this. Kindly help me in solving this issue.
    My SAP 8.81 patch level is: 5 and my DTW version is 88.1.4.
    CenterCode     CenterName     GroupCode     InWhichDimension     EffectiveFrom     
    CenterCode     CenterName     GroupCode     InWihchDimension     EffectiveFrom     
    SV-1     FORD FIERRA/PFL-128     SV     1     2011-01-01     
    SV-4     ISUZU ELF/UJZ-630             SV     1     2011-01-01
    Regards,
    Luz A. Cornejo

    Hi Luz,
    You're already said that you could successfully upload it in Test Run mode, so I don't think you made any mistake whatsoever with date format, field mapping rules, etc. considering if you made any mistake in that regard, you will get error message even in Test Run mode.
    I'm not sure if this could help you, but I once encountered same problem like you back then few years ago, if I remember correctly in SBO 2005. The very same problem, Test Run mode success, when I wanted to upload it permanently, error. The problem is, I didn't use DTW from latest patch. You said that you use PL 5 but your DTW PL 4. Maybe you should try upgrade your DTW to PL 5? Not sure if this helps, good luck.
    Best Regards,
    Hendry Wijaya

  • How to permit a transaction commit in applet?

    my code like this:
    Registry.set("secure.allowSaveFileFromApplets", JMFI18N.getResource("jmfregistry.settings.allowfilewrite") );
    Registry.set("secure.allowCaptureFromApplets", JMFI18N.getResource("jmfregistry.settings.allowcapture") );
    try {
    Registry.commit();
    catch (IOException ioe) {
    System.err.println("Error:"+ioe);
    I have signed the applet,but when execute,Exception as follows,
    java.lang.SecurityException: commit: Permission denied
         at com.Registry.commit(Registry.java:274)
         at com..JMFRegistry.doCommit(JMFRegistry.java:22)
    the line:Registry.commit(),sames use a transaction commit,but java.policy file no the permission,so,how to add the permission to the file?
    dying for help!!!
    s.

    I face with the same problem. i can do it in standalone java application but i cannot do the same thing in web start. i get the same "commit: Permission denied" exception. i got really stuck with the problem. i will greatly appreciate if you post the solution if you can find or found any.
    i will post any solution if i can find any.

  • Error  ESB to outbound AQ adapter - CCI Local Transaction COMMIT failed

    We are trying to enqueue a ESB message to a AQ adapter and recieve a "CCI Local Transaction COMMIT failed due to: SQL Error performing commit(). I have checked all the logs for both ESB and B2B to try to find out why this happening, but I am stuck and don't know where to go look next. We are running ESB 10.1.3.4 and B2B 10.1.2.3.
    Any information would help at this point.
    Here is what I see in the ESB logs:
    oracle.tip.esb.server.common.exceptions.BusinessEventRejectionException: Error occured while handling monitor message dequeued from monitor
    topic. Message text is "<activityMessages><activityMessage order='47' type='6'><flowId>pO9ODoC-ZkO7SVXEBy6IUA==</flowId><subFlowId>1236800149642</subFlowId><timestamp>1236800159806</timestamp><operationGUID>B6F20D90044311DEBF61EB90ED96C71E</operationGUID><
    perationQName>nsvs.cra.CRABirthSendebMS.Enqueue</operationQName><errorMessage><![CDATA[An unhandled exception has been thrown in the ESB
      system. The exception reported is: "org.collaxa.thirdparty.apache.wsif.WSIFException: esb:///ESB_Projects/ESBApplication_VitalStatsESBCRAProject/CRABirthSendebMS.wsdl
      [ Enqueue_ptt::Enqueue(CRAVitalEvent) ] - WSIF JCA Execute of operation 'Enqueue' failed due to: CCI Local Transaction COMMIT failed.
    CCI Local Transaction COMMIT failed due to: SQL Error performing commit().
    ; nested exception is:
    ORABPEL-11901
    CCI Local Transaction COMMIT failed.
    CCI Local Transaction COMMIT failed due to: SQL Error performing commit().
    Please examine the log file to determine the problem.
    at oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA.executeRequestResponseOperation(WSIFOperation_JCA.java:644)
    at oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA.executeInputOnlyOperation(WSIFOperation_JCA.java:739)
    at oracle.tip.esb.server.common.wsif.WSIFInvoker.executeOperation(WSIFInvoker.java:894)
    at oracle.tip.esb.server.common.wsif.WSIFInvoker.nextService(WSIFInvoker.java:810)
    at oracle.tip.esb.server.common.wsif.WSIFInvoker.nextService(WSIFInvoker.java:832)
    at oracle.tip.esb.server.service.impl.outadapter.OutboundAdapterService.nextService(OutboundAdapterService.java:223)
    at oracle.tip.esb.server.service.impl.outadapter.OutboundAdapterService.processBusinessEvent(OutboundAdapterService.java:135)
    at oracle.tip.esb.server.dispatch.InitialEventDispatcher.dispatchNonRoutingService(InitialEventDispatcher.java:406)
    at oracle.tip.esb.server.dispatch.InitialEventDispatcher.dispatch(InitialEventDispatcher.java:164)
    at oracle.tip.esb.server.dispatch.BusinessEvent.raise(BusinessEvent.java:1988)
    at oracle.tip.esb.server.dispatch.BusinessEvent.raise(BusinessEvent.java:1467)
    at oracle.tip.esb.utils.EventUtils.raiseBusinessEvent(EventUtils.java:205)
    at oracle.tip.esb.utils.EventUtils.raiseBusinessEvent(EventUtils.java:136)
    at oracle.tip.esb.server.service.EsbRouterSubscription.onBusinessEvent(EsbRouterSubscription.java:309)
    at oracle.tip.esb.server.dispatch.EventDispatcher.executeSubscription(EventDispatcher.java:138)
    at oracle.tip.esb.server.dispatch.InitialEventDispatcher.processSubscription(InitialEventDispatcher.java:545)
    at oracle.tip.esb.server.dispatch.InitialEventDispatcher.processSubscriptions(InitialEventDispatcher.java:527)
    at oracle.tip.esb.server.dispatch.EventDispatcher.dispatchRoutingService(EventDispatcher.java:94)
    at oracle.tip.esb.server.dispatch.InitialEventDispatcher.dispatch(InitialEventDispatcher.java:160)
    at oracle.tip.esb.server.dispatch.BusinessEvent.raise(BusinessEvent.java:1988)
    at oracle.tip.esb.server.dispatch.BusinessEvent.raise(BusinessEvent.java:1467)
    at oracle.tip.esb.utils.EventUtils.raiseBusinessEvent(EventUtils.java:205)
    at oracle.tip.esb.utils.EventUtils.raiseBusinessEvent(EventUtils.java:136)
    at oracle.tip.esb.server.service.EsbRouterSubscription.onBusinessEvent(EsbRouterSubscription.java:309)
    at oracle.tip.esb.server.dispatch.EventDispatcher.executeSubscription(EventDispatcher.java:138)
    at oracle.tip.esb.server.dispatch.InitialEventDispatcher.processSubscription(InitialEventDispatcher.java:545)
    at oracle.tip.esb.server.dispatch.InitialEventDispatcher.processSubscriptions(InitialEventDispatcher.java:527)
    at oracle.tip.esb.server.dispatch.EventDispatcher.dispatchRoutingService(EventDispatcher.java:94)
    at oracle.tip.esb.server.dispatch.InitialEventDispatcher.dispatch(InitialEventDispatcher.java:160)
    at oracle.tip.esb.server.dispatch.BusinessEvent.raise(BusinessEvent.java:1988)
    at oracle.tip.esb.server.dispatch.BusinessEvent.raise(BusinessEvent.java:1467)
    at oracle.tip.esb.utils.EventUtils.raiseBusinessEvent(EventUtils.java:205)
    at oracle.tip.esb.utils.EventUtils.raiseBusinessEvent(EventUtils.java:136)
    at oracle.tip.esb.server.service.EsbRouterSubscription.onBusinessEvent(EsbRouterSubscription.java:309)
    at oracle.tip.esb.server.dispatch.EventDispatcher.executeSubscription(EventDispatcher.java:138)
    at oracle.tip.esb.server.dispatch.InitialEventDispatcher.processSubscription(InitialEventDispatcher.java:545)
    at oracle.tip.esb.server.dispatch.InitialEventDispatcher.processSubscriptions(InitialEventDispatcher.java:527)
    at oracle.tip.esb.server.dispatch.EventDispatcher.dispatchRoutingService(EventDispatcher.java:94)
    at oracle.tip.esb.server.dispatch.InitialEventDispatcher.dispatch(InitialEventDispatcher.java:160)
    at oracle.tip.esb.server.dispatch.BusinessEvent.raise(BusinessEvent.java:1988)
    at oracle.tip.esb.server.dispatch.BusinessEvent.raise(BusinessEvent.java:1467)
    at oracle.tip.esb.utils.EventUtils.raiseBusinessEvent(EventUtils.java:119)
    at oracle.tip.esb.server.service.EsbRouterSubscription.processOperationResponse(EsbRouterSubscription.java:483)
    at oracle.tip.esb.server.service.EsbRouterSubscription.processEventResponse(EsbRouterSubscription.java:418)
    at oracle.tip.esb.server.service.EsbRouterSubscription.onBusinessEvent(EsbRouterSubscription.java:321)
    at oracle.tip.esb.server.dispatch.EventDispatcher.executeSubscription(EventDispatcher.java:138)
    at oracle.tip.esb.server.dispatch.InitialEventDispatcher.processSubscription(InitialEventDispatcher.java:545)
    at oracle.tip.esb.server.dispatch.InitialEventDispatcher.processSubscriptions(InitialEventDispatcher.java:527)
    at oracle.tip.esb.server.dispatch.EventDispatcher.dispatchRoutingService(EventDispatcher.java:94)
    at oracle.tip.esb.server.dispatch.InitialEventDispatcher.dispatch(InitialEventDispatcher.java:160)
    at oracle.tip.esb.server.dispatch.BusinessEvent.raise(BusinessEvent.java:1988)
    at oracle.tip.esb.server.dispatch.BusinessEvent.raise(BusinessEvent.java:1467)
    at oracle.tip.esb.utils.EventUtils.raiseBusinessEvent(EventUtils.java:205)
    at oracle.tip.esb.utils.EventUtils.raiseBusinessEvent(EventUtils.java:136)
    at oracle.tip.esb.server.service.EsbRouterSubscription.onBusinessEvent(EsbRouterSubscription.java:309)
    at oracle.tip.esb.server.dispatch.EventDispatcher.executeSubscription(EventDispatcher.java:138)
    at oracle.tip.esb.server.dispatch.InitialEventDispatcher.processSubscription(InitialEventDispatcher.java:545)
    at oracle.tip.esb.server.dispatch.InitialEventDispatcher.processSubscriptions(InitialEventDispatcher.java:527)
    at oracle.tip.esb.server.dispatch.EventDispatcher.dispatchRoutingService(EventDispatcher.java:94)
    at oracle.tip.esb.server.dispatch.InitialEventDispatcher.dispatch(InitialEventDispatcher.java:160)
    at oracle.tip.esb.server.dispatch.BusinessEvent.raise(BusinessEvent.java:1988)
    at oracle.tip.esb.server.dispatch.BusinessEvent.raise(BusinessEvent.java:1467)
    at oracle.tip.esb.utils.EventUtils.raiseBusinessEvent(EventUtils.java:119)
    at oracle.tip.esb.utils.EventUtils.raiseBusinessEvent(EventUtils.java:65)
    at oracle.tip.esb.server.service.impl.inadapter.ESBListenerImpl.processMessage(ESBListenerImpl.java:702)
    at oracle.tip.esb.server.service.impl.inadapter.ESBListenerImpl.onMessage(ESBListenerImpl.java:395)
    at oracle.tip.adapter.fw.jca.messageinflow.MessageEndpointImpl.onMessage(MessageEndpointImpl.java:307)
    at oracle.tip.adapter.db.InboundWork.onMessageImpl(InboundWork.java:1476)
    at oracle.tip.adapter.db.InboundWork.onMessage(InboundWork.java:1395)
    at oracle.tip.adapter.db.InboundWork.transactionalUnit(InboundWork.java:1349)
    at oracle.tip.adapter.db.InboundWork.runOnce(InboundWork.java:575)
    at oracle.tip.adapter.db.InboundWork.run(InboundWork.java:475)
    at oracle.tip.adapter.db.inbound.InboundWorkWrapper.run(InboundWorkWrapper.java:43)
    at oracle.j2ee.connector.work.WorkWrapper.runTargetWork(WorkWrapper.java:242)
    at oracle.j2ee.connector.work.WorkWrapper.doWork(WorkWrapper.java:215)
    at oracle.j2ee.connector.work.WorkWrapper.run(WorkWrapper.java:190)
    at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:830)
    at java.lang.Thread.run(Thread.java:595)
    Caused by: ORABPEL-11901
    CCI Local Transaction COMMIT failed.
    CCI Local Transaction COMMIT failed due to: SQL Error performing commit().
    Please examine the log file to determine the problem.
    at oracle.tip.adapter.aq.AQCciLocalTransactionImpl.commit(AQCciLocalTransactionImpl.java:89)
    at oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA.executeRequestResponseOperation(WSIFOperation_JCA.java:515)
    ... 77 more
    ]]></errorMessage><exception><![CDATA[oracle.tip.esb.server.common.exceptions.BusinessEventRetriableException: An unhandled exception
      has been thrown in the ESB system. The exception reported is: "org.collaxa.thirdparty.apache.wsif.WSIFException: esb:///ESB_Projects/ESBApplication_VitalStatsESBCRAProject/CRABirthSendebMS.wsdl
      [ Enqueue_ptt::Enqueue(CRAVitalEvent) ] - WSIF JCA Execute of operation 'Enqueue' failed due to: CCI Local Transaction COMMIT failed.
    CCI Local Transaction COMMIT failed due to: SQL Error performing commit().
    ; nested exception is:
    ORABPEL-11901
    CCI Local Transaction COMMIT failed.
    CCI Local Transaction COMMIT failed due to: SQL Error performing commit().
    Please examine the log file to determine the problem.
    at oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA.executeRequestResponseOperation(WSIFOperation_JCA.java:644)
    at oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA.executeInputOnlyOperation(WSIFOperation_JCA.java:739)
    at oracle.tip.esb.server.common.wsif.WSIFInvoker.executeOperation(WSIFInvoker.java:894)
    at oracle.tip.esb.server.common.wsif.WSIFInvoker.nextService(WSIFInvoker.java:810)
    at oracle.tip.esb.server.common.wsif.WSIFInvoker.nextService(WSIFInvoker.java:832)
    at oracle.tip.esb.server.service.impl.outadapter.OutboundAdapterService.nextService(OutboundAdapterService.java:223)
    at oracle.tip.esb.server.service.impl.outadapter.OutboundAdapterService.processBusinessEvent(OutboundAdapterService.java:135)
    at oracle.tip.esb.server.dispatch.InitialEventDispatcher.dispatchNonRoutingService(InitialEventDispatcher.java:406)
    at oracle.tip.esb.server.dispatch.InitialEventDispatcher.dispatch(InitialEventDispatcher.java:164)
    at oracle.tip.esb.server.dispatch.BusinessEvent.raise(BusinessEvent.java:1988)
    at oracle.tip.esb.server.dispatch.BusinessEvent.raise(BusinessEvent.java:1467)
    at oracle.tip.esb.utils.EventUtils.raiseBusinessEvent(EventUtils.java:205)
    at oracle.tip.esb.utils.EventUtils.raiseBusinessEvent(EventUtils.java:136)
    at oracle.tip.esb.server.service.EsbRouterSubscription.onBusinessEvent(EsbRouterSubscription.java:309)
    at oracle.tip.esb.server.dispatch.EventDispatcher.executeSubscription(EventDispatcher.java:138)
    at oracle.tip.esb.server.dispatch.InitialEventDispatcher.processSubscription(InitialEventDispatcher.java:545)
    at oracle.tip.esb.server.dispatch.InitialEventDispatcher.processSubscriptions(InitialEventDispatcher.java:527)
    at oracle.tip.esb.server.dispatch.EventDispatcher.dispatchRoutingService(EventDispatcher.java:94)
    at oracle.tip.esb.server.dispatch.InitialEventDispatcher.dispatch(InitialEventDispatcher.java:160)
    at oracle.tip.esb.server.dispatch.BusinessEvent.raise(BusinessEvent.java:1988)
    at oracle.tip.esb.server.dispatch.BusinessEvent.raise(BusinessEvent.java:1467)
    at oracle.tip.esb.utils.EventUtils.raiseBusinessEvent(EventUtils.java:205)
    at oracle.tip.esb.utils.EventUtils.raiseBusinessEvent(EventUtils.java:136)
    at oracle.tip.esb.server.service.EsbRouterSubscription.onBusinessEvent(EsbRouterSubscription.java:309)
    at oracle.tip.esb.server.dispatch.EventDispatcher.executeSubscription(EventDispatcher.java:138)
    at oracle.tip.esb.server.dispatch.InitialEventDispatcher.processSubscription(InitialEventDispatcher.java:545)
    at oracle.tip.esb.server.dispatch.InitialEventDispatcher.processSubscriptions(InitialEventDispatcher.java:527)
    at oracle.tip.esb.server.dispatch.EventDispatcher.dispatchRoutingService(EventDispatcher.java:94)
    at oracle.tip.esb.server.dispatch.InitialEventDispatcher.dispatch(InitialEventDispatcher.java:160)
    at oracle.tip.esb.server.dispatch.BusinessEvent.raise(BusinessEvent.java:1988)
    at oracle.tip.esb.server.dispatch.BusinessEvent.raise(BusinessEvent.java:1467)
    at oracle.tip.esb.utils.EventUtils.raiseBusinessEvent(EventUtils.java:205)
    at oracle.tip.esb.utils.EventUtils.raiseBusinessEvent(EventUtils.java:136)
    at oracle.tip.esb.server.service.EsbRouterSubscription.onBusinessEvent(EsbRouterSubscription.java:309)
    at oracle.tip.esb.server.dispatch.EventDispatcher.executeSubscriptio]]></exception><inPayload><![CDATA[<CRAVitalEvent>
    <Code/>
    <RecordTypeCode/>
    <Year/>
    <PlaceOfOccurrence>
    <City/>
    <CountryCode/>
    <ProvinceCode/>
    </PlaceOfOccurrence>
    <RegistrationNumber/>
    <AmendmentDate/>
    <Birth>
    <Child>
    <Name>
    <Surname/>
    <First/>
    <Second/>
    <Third/>
    </Name>
    <BirthDate/>
    <GenderCode/>
    </Child>
    <Mother>
    <Name>
    <MaidenName/>
    <Surname/>
    <First/>
    <Second/>
    <Third/>
    </Name>
    <SIN/>
    <BirthDate/>
    <BirthPlace>
    <ProvinceCode/>
    </BirthPlace>
    <UsualResidence>
    <StreetAddress/>
    <City/>
    <ProvinceCode/>
    <CountryCode/>
    <PostalCode/>
    </UsualResidence>
    </Mother>
    </Birth>
    </CRAVitalEvent>
    ]]></inPayload><retryable>false</retryable></activityMessage></activityMessages>"
    at oracle.tip.esb.monitor.manager.ActivityMessageReceiver.handleMessage(ActivityMessageReceiver.java:96)
    at oracle.tip.esb.server.dispatch.agent.ESBWork.process(ESBWork.java:178)
    at oracle.tip.esb.server.dispatch.agent.ESBWork.run(ESBWork.java:132)
    at oracle.j2ee.connector.work.WorkWrapper.runTargetWork(WorkWrapper.java:242)
    at oracle.j2ee.connector.work.WorkWrapper.doWork(WorkWrapper.java:215)
    at oracle.j2ee.connector.work.WorkWrapper.run(WorkWrapper.java:190)
    at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:825)
    at java.lang.Thread.run(Thread.java:595)
    Caused by: oracle.tip.esb.monitor.MonitorException: Due to the error "ORA-00904: "REQUEST_HEADER": invalid identifier
    ", the activity message could not be stored.
    at oracle.tip.esb.monitor.manager.database.AbstractFaultPersister.persist(AbstractFaultPersister.java:107)
    at oracle.tip.esb.monitor.manager.database.DBActivityMessageStore.persistMessage(DBActivityMessageStore.java:340)
    at oracle.tip.esb.monitor.manager.database.DBActivityMessageStore.store(DBActivityMessageStore.java:131)
    at oracle.tip.esb.monitor.manager.ActivityMessageReceiver.handleMessage(ActivityMessageReceiver.java:83)
    ... 7 more
    Caused by: java.sql.SQLException: ORA-00904: "REQUEST_HEADER": invalid identifier
    at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:138)
    at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:316)
    at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:282)
    at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:639)
    at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:185)
    at oracle.jdbc.driver.T4CPreparedStatement.execute_for_rows(T4CPreparedStatement.java:633)
    at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1161)
    at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3001)
    at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:3074)
    at oracle.oc4j.sql.proxy.PreparedStatementBCELProxy.executeUpdate(PreparedStatementBCELProxy.java:37)
    at oracle.tip.esb.monitor.manager.database.oracle.OracleFaultPersister.persist(OracleFaultPersister.java:137)
    at oracle.tip.esb.monitor.manager.database.AbstractFaultPersister.persist(AbstractFaultPersister.java:105)
    ... 10 more

    an updated output of the diagnostics logs are here:
    Throwing back the main exception PCRetriableResourceExceptionGeneric error.
    oracle.tip.esb.server.common.exceptions.BusinessEventRetriableException: An unhandled exception has been thrown in the ESB system.
    The exception reported is: "org.collaxa.thirdparty.apache.wsif.WSIFException: esb:///ESB_Projects/ESBApplication_VitalStatsESBCRAProject/CRABirthSendebMS.wsdl
    [ Enqueue_ptt::Enqueue(CRAVitalEvent) ] - WSIF JCA Execute of operation 'Enqueue' failed due to: CCI Local Transaction COMMIT failed.
    CCI Local Transaction COMMIT failed due to: SQL Error performing commit().
    ; nested exception is:
    ORABPEL-11901
    CCI Local Transaction COMMIT failed.
    CCI Local Transaction COMMIT failed due to: SQL Error performing commit().
    Please examine the log file to determine the problem.
    at oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA.executeRequestResponseOperation(WSIFOperation_JCA.java:644)
    at oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA.executeInputOnlyOperation(WSIFOperation_JCA.java:739)
    at oracle.tip.esb.server.common.wsif.WSIFInvoker.executeOperation(WSIFInvoker.java:894)
    at oracle.tip.esb.server.common.wsif.WSIFInvoker.nextService(WSIFInvoker.java:810)
    at oracle.tip.esb.server.common.wsif.WSIFInvoker.nextService(WSIFInvoker.java:832)
    at oracle.tip.esb.server.service.impl.outadapter.OutboundAdapterService.nextService(OutboundAdapterService.java:223)
    at oracle.tip.esb.server.service.impl.outadapter.OutboundAdapterService.processBusinessEvent(OutboundAdapterService.java:135)
    at oracle.tip.esb.server.dispatch.InitialEventDispatcher.dispatchNonRoutingService(InitialEventDispatcher.java:406)
    at oracle.tip.esb.server.dispatch.InitialEventDispatcher.dispatch(InitialEventDispatcher.java:164)
    at oracle.tip.esb.server.dispatch.BusinessEvent.raise(BusinessEvent.java:1988)
    at oracle.tip.esb.server.dispatch.BusinessEvent.raise(BusinessEvent.java:1467)
    at oracle.tip.esb.utils.EventUtils.raiseBusinessEvent(EventUtils.java:205)
    at oracle.tip.esb.utils.EventUtils.raiseBusinessEvent(EventUtils.java:136)
    at oracle.tip.esb.server.service.EsbRouterSubscription.onBusinessEvent(EsbRouterSubscription.java:309)
    at oracle.tip.esb.server.dispatch.EventDispatcher.executeSubscription(EventDispatcher.java:138)
    at oracle.tip.esb.server.dispatch.InitialEventDispatcher.processSubscription(InitialEventDispatcher.java:545)
    at oracle.tip.esb.server.dispatch.InitialEventDispatcher.processSubscriptions(InitialEventDispatcher.java:527)
    at oracle.tip.esb.server.dispatch.EventDispatcher.dispatchRoutingService(EventDispatcher.java:94)
    at oracle.tip.esb.server.dispatch.InitialEventDispatcher.dispatch(InitialEventDispatcher.java:160)
    at oracle.tip.esb.server.dispatch.BusinessEvent.raise(BusinessEvent.java:1988)
    at oracle.tip.esb.server.dispatch.BusinessEvent.raise(BusinessEvent.java:1467)
    at oracle.tip.esb.utils.EventUtils.raiseBusinessEvent(EventUtils.java:205)
    at oracle.tip.esb.utils.EventUtils.raiseBusinessEvent(EventUtils.java:136)
    at oracle.tip.esb.server.service.EsbRouterSubscription.onBusinessEvent(EsbRouterSubscription.java:309)
    at oracle.tip.esb.server.dispatch.EventDispatcher.executeSubscription(EventDispatcher.java:138)
    at oracle.tip.esb.server.dispatch.InitialEventDispatcher.processSubscription(InitialEventDispatcher.java:545)
    at oracle.tip.esb.server.dispatch.InitialEventDispatcher.processSubscriptions(InitialEventDispatcher.java:527)
    at oracle.tip.esb.server.dispatch.EventDispatcher.dispatchRoutingService(EventDispatcher.java:94)
    at oracle.tip.esb.server.dispatch.InitialEventDispatcher.dispatch(InitialEventDispatcher.java:160)
    at oracle.tip.esb.server.dispatch.BusinessEvent.raise(BusinessEvent.java:1988)
    at oracle.tip.esb.server.dispatch.BusinessEvent.raise(BusinessEvent.java:1467)
    at oracle.tip.esb.utils.EventUtils.raiseBusinessEvent(EventUtils.java:205)
    at oracle.tip.esb.utils.EventUtils.raiseBusinessEvent(EventUtils.java:136)
    at oracle.tip.esb.server.service.EsbRouterSubscription.onBusinessEvent(EsbRouterSubscription.java:309)
    at oracle.tip.esb.server.dispatch.EventDispatcher.executeSubscription(EventDispatcher.java:138)
    at oracle.tip.esb.server.dispatch.InitialEventDispatcher.processSubscription(InitialEventDispatcher.java:545)
    at oracle.tip.esb.server.dispatch.InitialEventDispatcher.processSubscriptions(InitialEventDispatcher.java:527)
    at oracle.tip.esb.server.dispatch.EventDispatcher.dispatchRoutingService(EventDispatcher.java:94)
    at oracle.tip.esb.server.dispatch.InitialEventDispatcher.dispatch(InitialEventDispatcher.java:160)
    at oracle.tip.esb.server.dispatch.BusinessEvent.raise(BusinessEvent.java:1988)
    at oracle.tip.esb.server.dispatch.BusinessEvent.raise(BusinessEvent.java:1467)
    at oracle.tip.esb.utils.EventUtils.raiseBusinessEvent(EventUtils.java:119)
    at oracle.tip.esb.server.service.EsbRouterSubscription.processOperationResponse(EsbRouterSubscription.java:483)
    at oracle.tip.esb.server.service.EsbRouterSubscription.processEventResponse(EsbRouterSubscription.java:418)
    at oracle.tip.esb.server.service.EsbRouterSubscription.onBusinessEvent(EsbRouterSubscription.java:321)
    at oracle.tip.esb.server.dispatch.EventDispatcher.executeSubscription(EventDispatcher.java:138)
    at oracle.tip.esb.server.dispatch.InitialEventDispatcher.processSubscription(InitialEventDispatcher.java:545)
    at oracle.tip.esb.server.dispatch.InitialEventDispatcher.processSubscriptions(InitialEventDispatcher.java:527)
    at oracle.tip.esb.server.dispatch.EventDispatcher.dispatchRoutingService(EventDispatcher.java:94)
    at oracle.tip.esb.server.dispatch.InitialEventDispatcher.dispatch(InitialEventDispatcher.java:160)
    at oracle.tip.esb.server.dispatch.BusinessEvent.raise(BusinessEvent.java:1988)
    at oracle.tip.esb.server.dispatch.BusinessEvent.raise(BusinessEvent.java:1467)
    at oracle.tip.esb.utils.EventUtils.raiseBusinessEvent(EventUtils.java:205)
    at oracle.tip.esb.utils.EventUtils.raiseBusinessEvent(EventUtils.java:136)
    at oracle.tip.esb.server.service.EsbRouterSubscription.onBusinessEvent(EsbRouterSubscription.java:309)
    at oracle.tip.esb.server.dispatch.EventDispatcher.executeSubscription(EventDispatcher.java:138)
    at oracle.tip.esb.server.dispatch.InitialEventDispatcher.processSubscription(InitialEventDispatcher.java:545)
    at oracle.tip.esb.server.dispatch.InitialEventDispatcher.processSubscriptions(InitialEventDispatcher.java:527)
    at oracle.tip.esb.server.dispatch.EventDispatcher.dispatchRoutingService(EventDispatcher.java:94)
    at oracle.tip.esb.server.dispatch.InitialEventDispatcher.dispatch(InitialEventDispatcher.java:160)
    at oracle.tip.esb.server.dispatch.BusinessEvent.raise(BusinessEvent.java:1988)
    at oracle.tip.esb.server.dispatch.BusinessEvent.raise(BusinessEvent.java:1467)
    at oracle.tip.esb.utils.EventUtils.raiseBusinessEvent(EventUtils.java:119)
    at oracle.tip.esb.utils.EventUtils.raiseBusinessEvent(EventUtils.java:65)
    at oracle.tip.esb.server.service.impl.inadapter.ESBListenerImpl.processMessage(ESBListenerImpl.java:702)
    at oracle.tip.esb.server.service.impl.inadapter.ESBListenerImpl.onMessage(ESBListenerImpl.java:395)
    at oracle.tip.adapter.fw.jca.messageinflow.MessageEndpointImpl.onMessage(MessageEndpointImpl.java:307)
    at oracle.tip.adapter.db.InboundWork.onMessageImpl(InboundWork.java:1476)
    at oracle.tip.adapter.db.InboundWork.onMessage(InboundWork.java:1395)
    at oracle.tip.adapter.db.InboundWork.transactionalUnit(InboundWork.java:1349)
    at oracle.tip.adapter.db.InboundWork.runOnce(InboundWork.java:575)
    at oracle.tip.adapter.db.InboundWork.run(InboundWork.java:475)
    at oracle.tip.adapter.db.inbound.InboundWorkWrapper.run(InboundWorkWrapper.java:43)
    at oracle.j2ee.connector.work.WorkWrapper.runTargetWork(WorkWrapper.java:242)
    at oracle.j2ee.connector.work.WorkWrapper.doWork(WorkWrapper.java:215)
    at oracle.j2ee.connector.work.WorkWrapper.run(WorkWrapper.java:190)
    at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:830)
    at java.lang.Thread.run(Thread.java:595)
    Caused by: ORABPEL-11901
    CCI Local Transaction COMMIT failed.
    CCI Local Transaction COMMIT failed due to: SQL Error performing commit().
    Please examine the log file to determine the problem.
    at oracle.tip.adapter.aq.AQCciLocalTransactionImpl.commit(AQCciLocalTransactionImpl.java:89)
    at oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA.executeRequestResponseOperation(WSIFOperation_JCA.java:515)
    ... 77 more
    at oracle.tip.esb.server.common.wsif.WSIFInvoker.executeOperation(WSIFInvoker.java:1015)
    at oracle.tip.esb.server.common.wsif.WSIFInvoker.nextService(WSIFInvoker.java:810)
    at oracle.tip.esb.server.common.wsif.WSIFInvoker.nextService(WSIFInvoker.java:832)
    at oracle.tip.esb.server.service.impl.outadapter.OutboundAdapterService.nextService(OutboundAdapterService.java:223)
    at oracle.tip.esb.server.service.impl.outadapter.OutboundAdapterService.processBusinessEvent(OutboundAdapterService.java:135)
    at oracle.tip.esb.server.dispatch.InitialEventDispatcher.dispatchNonRoutingService(InitialEventDispatcher.java:406)
    at oracle.tip.esb.server.dispatch.InitialEventDispatcher.dispatch(InitialEventDispatcher.java:164)
    at oracle.tip.esb.server.dispatch.BusinessEvent.raise(BusinessEvent.java:1988)
    at oracle.tip.esb.server.dispatch.BusinessEvent.raise(BusinessEvent.java:1467)
    at oracle.tip.esb.utils.EventUtils.raiseBusinessEvent(EventUtils.java:205)
    at oracle.tip.esb.utils.EventUtils.raiseBusinessEvent(EventUtils.java:136)
    at oracle.tip.esb.server.service.EsbRouterSubscription.onBusinessEvent(EsbRouterSubscription.java:309)
    at oracle.tip.esb.server.dispatch.EventDispatcher.executeSubscription(EventDispatcher.java:138)
    at oracle.tip.esb.server.dispatch.InitialEventDispatcher.processSubscription(InitialEventDispatcher.java:545)
    at oracle.tip.esb.server.dispatch.InitialEventDispatcher.processSubscriptions(InitialEventDispatcher.java:527)
    at oracle.tip.esb.server.dispatch.EventDispatcher.dispatchRoutingService(EventDispatcher.java:94)
    at oracle.tip.esb.server.dispatch.InitialEventDispatcher.dispatch(InitialEventDispatcher.java:160)
    at oracle.tip.esb.server.dispatch.BusinessEvent.raise(BusinessEvent.java:1988)
    at oracle.tip.esb.server.dispatch.BusinessEvent.raise(BusinessEvent.java:1467)
    at oracle.tip.esb.utils.EventUtils.raiseBusinessEvent(EventUtils.java:205)
    at oracle.tip.esb.utils.EventUtils.raiseBusinessEvent(EventUtils.java:136)
    at oracle.tip.esb.server.service.EsbRouterSubscription.onBusinessEvent(EsbRouterSubscription.java:309)
    at oracle.tip.esb.server.dispatch.EventDispatcher.executeSubscription(EventDispatcher.java:138)
    at oracle.tip.esb.server.dispatch.InitialEventDispatcher.processSubscription(InitialEventDispatcher.java:545)
    at oracle.tip.esb.server.dispatch.InitialEventDispatcher.processSubscriptions(InitialEventDispatcher.java:527)
    at oracle.tip.esb.server.dispatch.EventDispatcher.dispatchRoutingService(EventDispatcher.java:94)
    at oracle.tip.esb.server.dispatch.InitialEventDispatcher.dispatch(InitialEventDispatcher.java:160)
    at oracle.tip.esb.server.dispatch.BusinessEvent.raise(BusinessEvent.java:1988)
    at oracle.tip.esb.server.dispatch.BusinessEvent.raise(BusinessEvent.java:1467)
    at oracle.tip.esb.utils.EventUtils.raiseBusinessEvent(EventUtils.java:205)
    at oracle.tip.esb.utils.EventUtils.raiseBusinessEvent(EventUtils.java:136)
    at oracle.tip.esb.server.service.EsbRouterSubscription.onBusinessEvent(EsbRouterSubscription.java:309)
    at oracle.tip.esb.server.dispatch.EventDispatcher.executeSubscription(EventDispatcher.java:138)
    at oracle.tip.esb.server.dispatch.InitialEventDispatcher.processSubscription(InitialEventDispatcher.java:545)
    at oracle.tip.esb.server.dispatch.InitialEventDispatcher.processSubscriptions(InitialEventDispatcher.java:527)
    at oracle.tip.esb.server.dispatch.EventDispatcher.dispatchRoutingService(EventDispatcher.java:94)
    at oracle.tip.esb.server.dispatch.InitialEventDispatcher.dispatch(InitialEventDispatcher.java:160)
    at oracle.tip.esb.server.dispatch.BusinessEvent.raise(BusinessEvent.java:1988)
    at oracle.tip.esb.server.dispatch.BusinessEvent.raise(BusinessEvent.java:1467)
    at oracle.tip.esb.utils.EventUtils.raiseBusinessEvent(EventUtils.java:119)
    at oracle.tip.esb.server.service.EsbRouterSubscription.processOperationResponse(EsbRouterSubscription.java:483)
    at oracle.tip.esb.server.service.EsbRouterSubscription.processEventResponse(EsbRouterSubscription.java:418)
    at oracle.tip.esb.server.service.EsbRouterSubscription.onBusinessEvent(EsbRouterSubscription.java:321)
    at oracle.tip.esb.server.dispatch.EventDispatcher.executeSubscription(EventDispatcher.java:138)
    at oracle.tip.esb.server.dispatch.InitialEventDispatcher.processSubscription(InitialEventDispatcher.java:545)
    at oracle.tip.esb.server.dispatch.InitialEventDispatcher.processSubscriptions(InitialEventDispatcher.java:527)
    at oracle.tip.esb.server.dispatch.EventDispatcher.dispatchRoutingService(EventDispatcher.java:94)
    at oracle.tip.esb.server.dispatch.InitialEventDispatcher.dispatch(InitialEventDispatcher.java:160)
    at oracle.tip.esb.server.dispatch.BusinessEvent.raise(BusinessEvent.java:1988)
    at oracle.tip.esb.server.dispatch.BusinessEvent.raise(BusinessEvent.java:1467)
    at oracle.tip.esb.utils.EventUtils.raiseBusinessEvent(EventUtils.java:205)
    at oracle.tip.esb.utils.EventUtils.raiseBusinessEvent(EventUtils.java:136)
    at oracle.tip.esb.server.service.EsbRouterSubscription.onBusinessEvent(EsbRouterSubscription.java:309)
    at oracle.tip.esb.server.dispatch.EventDispatcher.executeSubscription(EventDispatcher.java:138)
    at oracle.tip.esb.server.dispatch.InitialEventDispatcher.processSubscription(InitialEventDispatcher.java:545)
    at oracle.tip.esb.server.dispatch.InitialEventDispatcher.processSubscriptions(InitialEventDispatcher.java:527)
    at oracle.tip.esb.server.dispatch.EventDispatcher.dispatchRoutingService(EventDispatcher.java:94)
    at oracle.tip.esb.server.dispatch.InitialEventDispatcher.dispatch(InitialEventDispatcher.java:160)
    at oracle.tip.esb.server.dispatch.BusinessEvent.raise(BusinessEvent.java:1988)
    at oracle.tip.esb.server.dispatch.BusinessEvent.raise(BusinessEvent.java:1467)
    at oracle.tip.esb.utils.EventUtils.raiseBusinessEvent(EventUtils.java:119)
    at oracle.tip.esb.utils.EventUtils.raiseBusinessEvent(EventUtils.java:65)
    at oracle.tip.esb.server.service.impl.inadapter.ESBListenerImpl.processMessage(ESBListenerImpl.java:702)
    at oracle.tip.esb.server.service.impl.inadapter.ESBListenerImpl.onMessage(ESBListenerImpl.java:395)
    at oracle.tip.adapter.fw.jca.messageinflow.MessageEndpointImpl.onMessage(MessageEndpointImpl.java:307)
    at oracle.tip.adapter.db.InboundWork.onMessageImpl(InboundWork.java:1476)
    at oracle.tip.adapter.db.InboundWork.onMessage(InboundWork.java:1395)
    at oracle.tip.adapter.db.InboundWork.transactionalUnit(InboundWork.java:1349)
    at oracle.tip.adapter.db.InboundWork.runOnce(InboundWork.java:575)
    at oracle.tip.adapter.db.InboundWork.run(InboundWork.java:475)
    at oracle.tip.adapter.db.inbound.InboundWorkWrapper.run(InboundWorkWrapper.java:43)
    at oracle.j2ee.connector.work.WorkWrapper.runTargetWork(WorkWrapper.java:242)
    at oracle.j2ee.connector.work.WorkWrapper.doWork(WorkWrapper.java:215)
    at oracle.j2ee.connector.work.WorkWrapper.run(WorkWrapper.java:190)
    at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:830)
    at java.lang.Thread.run(Thread.java:595)
    Caused by: org.collaxa.thirdparty.apache.wsif.WSIFException: esb:///ESB_Projects/ESBApplication_VitalStatsESBCRAProject/CRABirthSendebMS.wsdl
    [ Enqueue_ptt::Enqueue(CRAVitalEvent) ] - WSIF JCA Execute of operation 'Enqueue' failed due to: CCI Local Transaction COMMIT failed.
    CCI Local Transaction COMMIT failed due to: SQL Error performing commit().
    ; nested exception is:
    ORABPEL-11901
    CCI Local Transaction COMMIT failed.
    CCI Local Transaction COMMIT failed due to: SQL Error performing commit().
    Please examine the log file to determine the problem.
    at oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA.executeRequestResponseOperation(WSIFOperation_JCA.java:644)
    at oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA.executeInputOnlyOperation(WSIFOperation_JCA.java:739)
    at oracle.tip.esb.server.common.wsif.WSIFInvoker.executeOperation(WSIFInvoker.java:894)
    ... 75 more
    Caused by: ORABPEL-11901
    CCI Local Transaction COMMIT failed.
    CCI Local Transaction COMMIT failed due to: SQL Error performing commit().
    Please examine the log file to determine the problem.
    at oracle.tip.adapter.aq.AQCciLocalTransactionImpl.commit(AQCciLocalTransactionImpl.java:89)
    at oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA.executeRequestResponseOperation(WSIFOperation_JCA.java:515)
    ... 77 more
    [Caused by: CCI Local Transaction COMMIT failed.
        CCI Local Transaction COMMIT failed due to: SQL Error performing commit().
        Please examine the log file to determine the problem.
    Please create a Service Request with Oracle Support.
    ORABPEL-12600
    Generic error.
    oracle.tip.esb.server.common.exceptions.BusinessEventRetriableException: An unhandled exception has been thrown in the ESB system.
    The exception reported is: "org.collaxa.thirdparty.apache.wsif.WSIFException: esb:///ESB_Projects/ESBApplication_VitalStatsESBCRAProject/CRABirthSendebMS.wsdl
    [ Enqueue_ptt::Enqueue(CRAVitalEvent) ] - WSIF JCA Execute of operation 'Enqueue' failed due to: CCI Local Transaction COMMIT failed.
    CCI Local Transaction COMMIT failed due to: SQL Error performing commit().
    ; nested exception is:
    ORABPEL-11901
    CCI Local Transaction COMMIT failed.
    CCI Local Transaction COMMIT failed due to: SQL Error performing commit().
    Please examine the log file to determine the problem.
    at oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA.executeRequestResponseOperation(WSIFOperation_JCA.java:644)
    at oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA.executeInputOnlyOperation(WSIFOperation_JCA.java:739)
    at oracle.tip.esb.server.common.wsif.WSIFInvoker.executeOperation(WSIFInvoker.java:894)
    at oracle.tip.esb.server.common.wsif.WSIFInvoker.nextService(WSIFInvoker.java:810)
    at oracle.tip.esb.server.common.wsif.WSIFInvoker.nextService(WSIFInvoker.java:832)
    at oracle.tip.esb.server.service.impl.outadapter.OutboundAdapterService.nextService(OutboundAdapterService.java:223)
    at oracle.tip.esb.server.service.impl.outadapter.OutboundAdapterService.processBusinessEvent(OutboundAdapterService.java:135)
    at oracle.tip.esb.server.dispatch.InitialEventDispatcher.dispatchNonRoutingService(InitialEventDispatcher.java:406)
    at oracle.tip.esb.server.dispatch.InitialEventDispatcher.dispatch(InitialEventDispatcher.java:164)
    at oracle.tip.esb.server.dispatch.BusinessEvent.raise(BusinessEvent.java:1988)
    at oracle.tip.esb.server.dispatch.BusinessEvent.raise(BusinessEvent.java:1467)
    at oracle.tip.esb.utils.EventUtils.raiseBusinessEvent(EventUtils.java:205)
    at oracle.tip.esb.utils.EventUtils.raiseBusinessEvent(EventUtils.java:136)
    at oracle.tip.esb.server.service.EsbRouterSubscription.onBusinessEvent(EsbRouterSubscription.java:309)
    at oracle.tip.esb.server.dispatch.EventDispatcher.executeSubscription(EventDispatcher.java:138)
    at oracle.tip.esb.server.dispatch.InitialEventDispatcher.processSubscription(InitialEventDispatcher.java:545)
    at oracle.tip.esb.server.dispatch.InitialEventDispatcher.processSubscriptions(InitialEventDispatcher.java:527)
    at oracle.tip.esb.server.dispatch.EventDispatcher.dispatchRoutingService(EventDispatcher.java:94)
    at oracle.tip.esb.server.dispatch.InitialEventDispatcher.dispatch(InitialEventDispatcher.java:160)
    at oracle.tip.esb.server.dispatch.BusinessEvent.raise(BusinessEvent.java:1988)
    at oracle.tip.esb.server.dispatch.BusinessEvent.raise(BusinessEvent.java:1467)
    at oracle.tip.esb.utils.EventUtils.raiseBusinessEvent(EventUtils.java:205)
    at oracle.tip.esb.utils.EventUtils.raiseBusinessEvent(EventUtils.java:136)
    at oracle.tip.esb.server.service.EsbRouterSubscription.onBusinessEvent(EsbRouterSubscription.java:309)
    at oracle.tip.esb.server.dispatch.EventDispatcher.executeSubscription(EventDispatcher.java:138)
    at oracle.tip.esb.server.dispatch.InitialEventDispatcher.processSubscription(InitialEventDispatcher.java:545)
    at oracle.tip.esb.server.dispatch.InitialEventDispatcher.processSubscriptions(InitialEventDispatcher.java:527)
    at oracle.tip.esb.server.dispatch.EventDispatcher.dispatchRoutingService(EventDispatcher.java:94)
    at oracle.tip.esb.server.dispatch.InitialEventDispatcher.dispatch(InitialEventDispatcher.java:160)
    at oracle.tip.esb.server.dispatch.BusinessEvent.raise(BusinessEvent.java:1988)
    at oracle.tip.esb.server.dispatch.BusinessEvent.raise(BusinessEvent.java:1467)
    at oracle.tip.esb.utils.EventUtils.raiseBusinessEvent(EventUtils.java:205)
    at oracle.tip.esb.utils.EventUtils.raiseBusinessEvent(EventUtils.java:136)
    at oracle.tip.esb.server.service.EsbRouterSubscription.onBusinessEvent(EsbRouterSubscription.java:309)
    at oracle.tip.esb.server.dispatch.EventDispatcher.executeSubscription(EventDispatcher.java:138)
    at oracle.tip.esb.server.dispatch.InitialEventDispatcher.processSubscription(InitialEventDispatcher.java:545)
    at oracle.tip.esb.server.dispatch.InitialEventDispatcher.processSubscriptions(InitialEventDispatcher.java:527)
    at oracle.tip.esb.server.dispatch.EventDispatcher.dispatchRoutingService(EventDispatcher.java:94)
    at oracle.tip.esb.server.dispatch.InitialEventDispatcher.dispatch(InitialEventDispatcher.java:160)
    at oracle.tip.esb.server.dispatch.BusinessEvent.raise(BusinessEvent.java:1988)
    at oracle.tip.esb.server.dispatch.BusinessEvent.raise(BusinessEvent.java:1467)
    at oracle.tip.esb.utils.EventUtils.raiseBusinessEvent(EventUtils.java:119)
    at oracle.tip.esb.server.service.EsbRouterSubscription.processOperationResponse(EsbRouterSubscription.java:483)
    at oracle.tip.esb.server.service.EsbRouterSubscription.processEventResponse(EsbRouterSubscription.java:418)
    at oracle.tip.esb.server.service.EsbRouterSubscription.onBusinessEvent(EsbRouterSubscription.java:321)
    at oracle.tip.esb.server.dispatch.EventDispatcher.executeSubscription(EventDispatcher.java:138)
    at oracle.tip.esb.server.dispatch.InitialEventDispatcher.processSubscription(InitialEventDispatcher.java:545)
    at oracle.tip.esb.server.dispatch.InitialEventDispatcher.processSubscriptions(InitialEventDispatcher.java:527)
    at oracle.tip.esb.server.dispatch.EventDispatcher.dispatchRoutingService(EventDispatcher.java:94)
    at oracle.tip.esb.server.dispatch.InitialEventDispatcher.dispatch(InitialEventDispatcher.java:160)
    at oracle.tip.esb.server.dispatch.BusinessEvent.raise(BusinessEvent.java:1988)
    at oracle.tip.esb.server.dispatch.BusinessEvent.raise(BusinessEvent.java:1467)
    at oracle.tip.esb.utils.EventUtils.raiseBusinessEvent(EventUtils.java:205)
    at oracle.tip.esb.utils.EventUtils.raiseBusinessEvent(EventUtils.java:136)
    at oracle.tip.esb.server.service.EsbRouterSubscription.onBusinessEvent(EsbRouterSubscription.java:309)
    at oracle.tip.esb.server.dispatch.EventDispatcher.executeSubscription(EventDispatcher.java:138)
    at oracle.tip.esb.server.dispatch.InitialEventDispatcher.processSubscription(InitialEventDispatcher.java:545)
    at oracle.tip.esb.server.dispatch.InitialEventDispatcher.processSubscriptions(InitialEventDispatcher.java:527)
    at oracle.tip.esb.server.dispatch.EventDispatcher.dispatchRoutingService(EventDispatcher.java:94)
    at oracle.tip.esb.server.dispatch.InitialEventDispatcher.dispatch(InitialEventDispatcher.java:160)
    at oracle.tip.esb.server.dispatch.BusinessEvent.raise(BusinessEvent.java:1988)
    at oracle.tip.esb.server.dispatch.BusinessEvent.raise(BusinessEvent.java:1467)
    at oracle.tip.esb.utils.EventUtils.raiseBusinessEvent(EventUtils.java:119)
    at oracle.tip.esb.utils.EventUtils.raiseBusinessEvent(EventUtils.java:65)
    at oracle.tip.esb.server.service.impl.inadapter.ESBListenerImpl.processMessage(ESBListenerImpl.java:702)
    at oracle.tip.esb.server.service.impl.inadapter.ESBListenerImpl.onMessage(ESBListenerImpl.java:395)
    at oracle.tip.adapter.fw.jca.messageinflow.MessageEndpointImpl.onMessage(MessageEndpointImpl.java:307)
    at oracle.tip.adapter.db.InboundWork.onMessageImpl(InboundWork.java:1476)
    at oracle.tip.adapter.db.InboundWork.onMessage(InboundWork.java:1395)
    at oracle.tip.adapter.db.InboundWork.transactionalUnit(InboundWork.java:1349)
    at oracle.tip.adapter.db.InboundWork.runOnce(InboundWork.java:575)
    at oracle.tip.adapter.db.InboundWork.run(InboundWork.java:475)
    at oracle.tip.adapter.db.inbound.InboundWorkWrapper.run(InboundWorkWrapper.java:43)
    at oracle.j2ee.connector.work.WorkWrapper.runTargetWork(WorkWrapper.java:242)
    at oracle.j2ee.connector.work.WorkWrapper.doWork(WorkWrapper.java:215)
    at oracle.j2ee.connector.work.WorkWrapper.run(WorkWrapper.java:190)
    at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:830)
    at java.lang.Thread.run(Thread.java:595)
    Caused by: ORABPEL-11901
    CCI Local Transaction COMMIT failed.
    CCI Local Transaction COMMIT failed due to: SQL Error performing commit().
    Please examine the log file to determine the problem.

  • DBMS_BLOB: ORA-22297: warning: Open LOBs exist at transaction commit time

    Hello
    I've written this to get to understand BLOBS. I had intended it to take a VARCHAR2 string, convert it to RAW and write the contents to a blob.
    However, DBMS_LOB.Write()) returns the error message "ORA-22297: warning: Open LOBs exist at transaction commit time". Can somebody put me right? Just why is this being returned?
    Thanks in advance, Aidan
    INSERT INTO BINARY (PK ,
    BLOBDATA )
    VALUES (1 ,
    Empty_Blob());                         
    /* Lock the row. */
    SELECT BLOBDATADATA INTO V_Blob FROM BINARY WHERE PK = 1 FOR UPDATE;                                             
    /* Open the Lob. */
    DBMS_LOB.OPEN (V_Blob, DBMS_LOB.LOB_READWRITE);
    DBMS_LOB.WRITE (V_Blob ,
    V_Length ,
         V_Offset ,
    UTL_RAW.CAST_TO_RAW (p_Data));
    DBMS_LOB.CLOSE (V_Blob);

    I get the abocve error when running using the GUI
    when running from command prompt i get the following
    begin
       -- Remove Application
    wwv_flow_api.remove_flow(nvl(wwv_flow_application_install.get_application_id,99000));
    end;
    ORA-20001: Package variable g_security_group_id must be set.
    ORA-06512: at "APEX_040200.WWV_FLOW_API", line 998
    ORA-06512: at "APEX_040200.WWV_FLOW_API", line 1569
    ORA-06512: at line 5
    I am assuming there are some permissions problems
    I have DBA role in Database
    We are on databasae > 11 (11.0.2 i think)
    My database DBA installed 4.2.2 but does know APEX real well he installed becasue he has SYS password which I am not privy to.
    I was able to install Pacakaged appliaction.
    Kind of Lost from Here.......
    I am assuming i have a permissions error
    I have DBA role in Database

  • CCI Local Transaction COMMIT failed due to: ERRJMS_COMMIT_FAIL.

    Dear All,
    I am using a JMS adapter in my BPEL Process. and was getting the following error in the Audit Instance:
    file:/u03/soauser/product/10.1.3.1/OracleAS_1/bpel/domains/default/tmp/.bpel_DiaryQuery_1.0_1f16ddcb57197b9c85f6b130f580956d.tmp/DiaryQueryMergedReqResp.wsdl [ DiaryQueryMsgProduce_ptt::DiaryQueryMsgProduce(DiaryQueryRequest) ] - WSIF JCA Execute of operation 'DiaryQueryMsgProduce' failed due to: ERRJMS_TRX_COMMIT.
    CCI Local Transaction COMMIT failed due to: ERRJMS_COMMIT_FAIL.
    Unable to commit transaction.
    Please examine the log file to determine the problem.
    ; nested exception is:
         ORABPEL-12101
    ERRJMS_TRX_COMMIT.
    CCI Local Transaction COMMIT failed due to: ERRJMS_COMMIT_FAIL.
    Unable to commit transaction.
    What could be the problem for this. How can I fix this..
    Please update....
    Many Thanks in advance...

    In the JMS configuration (oc4j-ra.xml), set the following property to false:
    <config-property name="isTransacted" value="false"/>

  • DTW Transaction Commit Unsuccessful

    Hi All,
    I'm using DTW version 2005.0.29.  When I tried to import transaction, it gave me error message "Transaction Commit Unsuccessful".  I would like to know what's causes it.
    Regards,
    Foong Yee

    Hi Foong,
    Here is the solution from SAP note:
    DTW 2005.0.27: Handling a Transaction Commit Failure
    Symptom
    If a transaction commit operation is unsuccessful, for example, the stored procedure SBO_SP_TransactionNotification failure leads to a failed transaction commit, Data Transfer Workbench shows a successful import, even though the data has not been imported.
    Other terms
    DTW, Data Transfer Workbench, B1, SAP Business One, Transaction, Commit
    Reason and Prerequisites
    Bug
    Solution
    An upgrade to DTW2005.0.27 includes this functionality. If a transaction commit operation is unsuccessful, Data Transfer Workbench shows the import as failed and generates an error message.
    Based on the note above, I think it is a bug of DTW you are currently using. I suggest to upgrade the DTW version including the DI API version so that the DTW can run.
    Rgds,
    JimM

  • Connection is closed after transaction commit

    WebLogic 10.3.0.0, Oracle 10gXE, JPA is provided by EclipseLink v1.1.2.v20090612-r4475.
    Transactions are managed by WLS.
    There is a stateless bean
    @Stateless()
    @TransactionAttribute(TransactionAttributeType.REQUIRED)
    @TransactionManagement(value = TransactionManagementType.CONTAINER)
    public class ServiceFacadeBean
    @TransactionAttribute(TransactionAttributeType.REQUIRES_NEW)
    public void processResponse(....){
    //operations with DB
    which is instantiated by two concurrent threads.
    After one of the threads commits transaction, the other finds connection (or just statement) closed. For instance,
    ####<03.02.2010 10:10:04 MSK> <Notice> <Stdout> <spbnb-prc32> <AdminServer> <[ACTIVE] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1265181004591> <BEA-000000> <[EL Finer]: 2010-02-03 10:10:04.591--UnitOfWork(10135841)--Thread(Thread[[ACTIVE] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)',5,Pooled Threads])--TX afterCompletion callback, status=COMMITTED>
    ####<03.02.2010 10:10:04 MSK> <Notice> <Stdout> <spbnb-prc32> <AdminServer> <[ACTIVE] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1265181004591> <BEA-000000> <[EL Finer]: 2010-02-03 10:10:04.591--UnitOfWork(10135841)--Thread(Thread[[ACTIVE] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)',5,Pooled Threads])--end unit of work commit>
    ####<03.02.2010 10:10:04 MSK> <Notice> <Stdout> <spbnb-prc32> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1265181004607> <BEA-000000> <[EL Warning]: 2010-02-03 10:10:04.591--UnitOfWork(10135841)--Thread(Thread[[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)',5,Pooled Threads])--Local Exception Stack:
    Exception [EclipseLink-4002] (Eclipse Persistence Services - 1.1.2.v20090612-r4475): org.eclipse.persistence.exceptions.DatabaseException
    Internal Exception: java.sql.SQLException: Statement has already been closed
    Error Code: 0
    Call: UPDATE TASK SET TSK_RESULT = ?, TSK_PROCESS_STATE = ?, TSK_END_TS = ?, TSK_CREATE_TS = ?, TSK_CHANGE_TS = ? WHERE (TSK_ID = ?)
         bind => [<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
    , 4, 2010-02-03 10:10:04.435, 2010-02-03 10:10:04.435, 2010-02-03 10:10:04.435, 41]
    Query: UpdateObjectQuery(com.tsystems.tenergy.smp.mds.persistence.domain.Task@7bc43e)
         at org.eclipse.persistence.exceptions.DatabaseException.sqlException(DatabaseException.java:332)
         at org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.basicExecuteCall(DatabaseAccessor.java:656)
         at org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.executeCall(DatabaseAccessor.java:501)
         at org.eclipse.persistence.internal.sessions.AbstractSession.executeCall(AbstractSession.java:872)
         at org.eclipse.persistence.internal.queries.DatasourceCallQueryMechanism.executeCall(DatasourceCallQueryMechanism.java:205)
         at org.eclipse.persistence.internal.queries.DatasourceCallQueryMechanism.executeCall(DatasourceCallQueryMechanism.java:191)
         at org.eclipse.persistence.internal.queries.DatasourceCallQueryMechanism.updateObject(DatasourceCallQueryMechanism.java:686)
         at org.eclipse.persistence.internal.queries.StatementQueryMechanism.updateObject(StatementQueryMechanism.java:430)
         at org.eclipse.persistence.internal.queries.DatabaseQueryMechanism.updateObjectForWriteWithChangeSet(DatabaseQueryMechanism.java:1135)
         at org.eclipse.persistence.queries.UpdateObjectQuery.executeCommitWithChangeSet(UpdateObjectQuery.java:84)
         at org.eclipse.persistence.internal.queries.DatabaseQueryMechanism.executeWriteWithChangeSet(DatabaseQueryMechanism.java:286)
         at org.eclipse.persistence.queries.WriteObjectQuery.executeDatabaseQuery(WriteObjectQuery.java:58)
         at org.eclipse.persistence.queries.DatabaseQuery.execute(DatabaseQuery.java:664)
         at org.eclipse.persistence.queries.DatabaseQuery.executeInUnitOfWork(DatabaseQuery.java:583)
         at org.eclipse.persistence.queries.ObjectLevelModifyQuery.executeInUnitOfWorkObjectLevelModifyQuery(ObjectLevelModifyQuery.java:109)
         at org.eclipse.persistence.queries.ObjectLevelModifyQuery.executeInUnitOfWork(ObjectLevelModifyQuery.java:86)
         at org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.internalExecuteQuery(UnitOfWorkImpl.java:2756)
         at org.eclipse.persistence.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:1181)
         at org.eclipse.persistence.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:1165)
         at org.eclipse.persistence.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:1125)
         at org.eclipse.persistence.internal.sessions.CommitManager.commitChangedObjectsForClassWithChangeSet(CommitManager.java:232)
         at org.eclipse.persistence.internal.sessions.CommitManager.commitAllObjectsForClassWithChangeSet(CommitManager.java:163)
         at org.eclipse.persistence.internal.sessions.CommitManager.commitAllObjectsWithChangeSet(CommitManager.java:116)
         at org.eclipse.persistence.internal.sessions.AbstractSession.writeAllObjectsWithChangeSet(AbstractSession.java:3175)
         at org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.commitToDatabase(UnitOfWorkImpl.java:1299)
         at org.eclipse.persistence.internal.sessions.RepeatableWriteUnitOfWork.commitToDatabase(RepeatableWriteUnitOfWork.java:469)
         at org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.commitToDatabaseWithChangeSet(UnitOfWorkImpl.java:1399)
         at org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.issueSQLbeforeCompletion(UnitOfWorkImpl.java:3023)
         at org.eclipse.persistence.internal.sessions.RepeatableWriteUnitOfWork.issueSQLbeforeCompletion(RepeatableWriteUnitOfWork.java:224)
         at org.eclipse.persistence.transaction.AbstractSynchronizationListener.beforeCompletion(AbstractSynchronizationListener.java:157)
         at org.eclipse.persistence.transaction.JTASynchronizationListener.beforeCompletion(JTASynchronizationListener.java:68)
         at weblogic.transaction.internal.ServerSCInfo.doBeforeCompletion(ServerSCInfo.java:1217)
         at weblogic.transaction.internal.ServerSCInfo.callBeforeCompletions(ServerSCInfo.java:1195)
         at weblogic.transaction.internal.ServerSCInfo.startPrePrepareAndChain(ServerSCInfo.java:118)
         at weblogic.transaction.internal.ServerTransactionImpl.localPrePrepareAndChain(ServerTransactionImpl.java:1302)
         at weblogic.transaction.internal.ServerTransactionImpl.globalPrePrepare(ServerTransactionImpl.java:2114)
         at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:263)
         at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:230)
         at weblogic.ejb.container.internal.BaseRemoteObject.postInvoke1(BaseRemoteObject.java:621)
         at weblogic.ejb.container.internal.StatelessRemoteObject.postInvoke1(StatelessRemoteObject.java:60)
         at weblogic.ejb.container.internal.BaseRemoteObject.postInvokeTxRetry(BaseRemoteObject.java:441)
         at com.tsystems.tenergy.smp.mds.service.impl.MDSServiceFacadeBean_dv9pfe_MDSServiceFacadeImpl.processMCSResponse(MDSServiceFacadeBean_dv9pfe_MDSServiceFacadeImpl.java:243)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:597)
         at weblogic.ejb.container.internal.RemoteBusinessIntfProxy.invoke(RemoteBusinessIntfProxy.java:69)
         at $Proxy174.processMCSResponse(Unknown Source)
         at com.tsystems.tenergy.smp.mds.access.impl.MCSResponseProcessor.processMessage(MCSResponseProcessor.java:44)
         at com.tsystems.tenergy.smp.mds.access.MDSJMSServiceAdaptor.handleMessage(MDSJMSServiceAdaptor.java:41)
         at com.tsystems.tenergy.smp.common.access.impl.AbstractJMSServiceAdaptor.onMessage(AbstractJMSServiceAdaptor.java:55)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:597)
         at com.bea.core.repackaged.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:281)
         at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:187)
         at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:154)
         at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:126)
         at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:114)
         at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:176)
         at com.bea.core.repackaged.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:89)
         at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:176)
         at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:126)
         at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:114)
         at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:176)
         at com.bea.core.repackaged.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:210)
         at $Proxy194.onMessage(Unknown Source)
         at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:466)
         at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:371)
         at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:327)
         at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:4547)
         at weblogic.jms.client.JMSSession.execute(JMSSession.java:4233)
         at weblogic.jms.client.JMSSession.executeMessage(JMSSession.java:3709)
         at weblogic.jms.client.JMSSession.access$000(JMSSession.java:114)
         at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:5058)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    Caused by: java.sql.SQLException: Statement has already been closed
         at weblogic.jdbc.wrapper.Statement.checkStatement(Statement.java:305)
         at weblogic.jdbc.wrapper.Statement.preInvocationHandler(Statement.java:116)
         at weblogic.jdbc.wrapper.PreparedStatement_weblogic_jdbc_base_BasePreparedStatement.getWarnings(Unknown Source)
         at org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.basicExecuteCall(DatabaseAccessor.java:638)
         ... 77 more>
    I would be very thankful for any help... I'm fighting with the bug already 4 days but there is still no result.....

    You need to make sure all your JDBC objects are method-level, not class or instance variables.
    Otherwise you may have two threads trying to use the same connection or statement, and
    the first one to complete a transaction may cause the connection and it's subobjects to
    be closed.

  • Transaction commit in database adapter

    Hi,
    When the commit happens when a database adapter inserts a record.
    I have two invoke process one is db adapter to insert records and second the db adapter to call the procedure to update the records inserted by first adapter, but will the records will be visible in the second adapter.
    Please advice, thanks in advance.
    Regards,
    SReejit

    Yes because it is one transaction, therfore you can roll back if the second fails.
    But if you perform a dehydration, e.g. wait, human task, receive activity then the first insert will be committed. so you will not be able to roll back. You will need to use a compensate activity.
    cheers
    James

  • Distributed JDBC/JMS transaction commit order

    I am using WLS 10.3.0. I have an app with container-managed EJBs which participate in distributed transactions using XA drivers for two resources, (1) a jdbc connection to Oracle database, and (2) WebLogic JMS server. In a typical EJB call, I am writing a record to the database and sending a message to a local queue which is being consumed by a MDB. My question is how can I guarantee that by the time the MDB receives the JMS message, the record will be guaranteed to have been committed in the database. It appears that occasionally the record is not yet there. Is there a way to force the jdbc commit to happen before the JMS message gets consumed? I know there is a commit_point_strength parameter that determines commit order for the database resource, but I don't see such a concept for JMS...

    "The Default Time-to-Deliver attribute for XAConnectionFactory for the Weblogic JMS connection queue, is a minimum interval from when the message is SENT, to when it is available to be processed. What is really needed is a delay from COMMIT time -- not from the sent time."
    <jay>
    Not entirely true. Delay is not from when message is “SENT, Default Time-To-Deliver is delay at within JMS subsystem before it delivers message to consumer. It means that "Send" thread will not block for this delay and "Send" side executes no different whether there is "Time-to-Deliver" configured or not.
    </jay>
    "For example, imagine a distributed transaction does a JMS send, followed by a query that takes 10 seconds, followed by a commit. If Default Time-to-Deliver is set to 5 seconds, it will be completly ignored, since the 10 seconds from the send to the commit is a larger interval. So at commit it is still very possible that the MDB will receive the message before the database transaction is committed."
    <jay>
    This is not true also. JMS message will be available for delivery only after distributed transaction commits and more specifically "commit" part of the JMS resource completes - clock for "message delivery delay" will not start until distributed transaction is committed. Considering transaction will not commit until slow running query completes execution above scenario will not cause “Default Time-to-Deliver” workaround to fail.
    Slow execution of the XA.commit() request from TM (Weblogic) to database may cause concern , however considering that TM (WebLogic) receive response of the XA.prepare() from all participating resources before XA.commit(), commit should execute with delay not more than few milliseconds and chances are negligible that proposed workaround will fail.
    </jay>
    "The bottom line, is that this parameter is not an effective way to control the race condition unless the JMS send is always performed as the last action in a distributed transaction.
    For this reason we have gone with inserting a small configurable sleep at the start of the onMessage() methods in the MDB. Not a very elegant solution, but the one ne that works reliably."
    <jay>
    I think "Default Time-to-Deliver" is no less effective or no less reliable solution than placing sleep() in onMessage(), however it is more cleaner solution because it uses application server built in feature instead of updating code in onMessage().
    </jay>
    -jayesh@yagna

  • JMS Sender with ejb3 container managed transaction

    Hi all,
    I refer to the following link http://download.oracle.com/docs/cd/E11035_01/wls100/jms/trans.html#wp1035937
    I found that JTA support JMS.
    But I dont' want to use JTA explicitly, I want to use container manage transaction. eg. inside ejb3 stateless session bean.
    does it support JMS?
    With Regards,
    wp

    Hi,
    Yes, WebLogic JMS supports JTA (a.k.a XA, a.k.a global) transactions such as container managed transactions. There are two requirements for CMTs on SSB:
    (1) use an XML descriptor setting or EJB annotation to enable CMT for the SSB
    (2) use a WebLogic JMS connection factory that is configured to have "global (XA) transactions enabled"
    And I usually also recommend:
    (3) Consider using a JEE "res-ref" for the connection factory to enable pooling of JMS resources. See "Enhanced Support for Using WebLogic JMS with EJBs and Servlets" (http://download.oracle.com/docs/cd/E14571_01/web.1111/e13727/j2ee.htm#g1329180), and the "Integrating Remote JMS Providers" FAQ (http://download.oracle.com/docs/cd/E14571_01/web.1111/e13727/interop.htm#JMSPG553).
    (4) Avoid using SSBs to receive messages. MDBs are specifically designed for processing incoming messages.
    It's also possible to have WebLogic automatically enlist foreign (non-WebLogic) vendors in WebLogic transactions. See the "Integrating Remote JMS Providers" FAQ for details (http://download.oracle.com/docs/cd/E14571_01/web.1111/e13727/interop.htm#JMSPG553).
    Regards,
    tom

  • JCA / JDBC Configured for non-XA Attempting XA Transaction Commit

    I am attempting to create simple BPEL SOA composites in SOA 11.1.1.5 that use a DbAdapter to execute a stored procedure in an 11g database. The database task being performed only involves a single database and does not require transaction support. I have carefully stepped through the creation of the DataSource and JCA pointing through the DbAdapter to the JDBC DataSource so XA transaction support is disabled, the JCA pool sets the transaction mode to "No transaction" and the JCA pool uses the dataSource value to point to the JNDI name of the JDBC pool rather than the xADataSource value.
    Visually,
    DataSource definition:
    name = jdbc/myserviceDataSource
    driver = oracle.jdbc.xa.client.OracleXADataSource
    url = jdbc:oracle:thin:@mydbhost.myfirm.com:1521:GENERIC
    use XA DataSource = unchecked
    set XA timeout = unchecked
    Keep XA connection until transaction complete = checked
    keep connection after local transaction = checked
    JCA definition:
    name = eis/DB/myserviceDataSource
    dataSourceName = jdbc/myserviceDataSource
    xADataSourceName = (blank)
    platform class name = org.eclipse.persistence.platform.database.Oracle10Platform
    Transaction | Transaction Support: no transaction
    This configuration works on one sandbox server and I got it working in a second sandbox server. However, after deleting the JDBC and JCA pools to go through the process one more time to document the procedure on the second server, I am unable to get the configuration working again. The WebLogic domain appears to be resurrecting portions of an old configuration that still references the JNDI name of the JDBC pool in the xADataSourceName parameter. I have unpacked the DbAdapter.rar archive for the DbAdapter and verified the contents of the ./META-INF/weblogic-ra.xml file don't use the xADataSouceName parameter. The Deployment Plan for the DbAdapter (named DbAdapterPlan.xml in $SOA_HOME/soa/connectors ) also explicitly configures the JCA pool using the dataSourceName value leaving the xADataSourceName value blank.
    However, executing the SOA service using this JCA connection results in this error:
    java.sql.SQLException: Cannot call Connection.commit in distributed transaction.
    Again, I know the theoretical answer to this question is to disable transactions in the JCA and JDBC configurations and don't use the xADataSourceName element of the JCA configuration to point to the JDBC pool. However, after validating those elements and restarting the pools or performing an Update on the DbAdapter deployment, WebLogic seems to still create connections through the JDBC pool with transactions enabled.
    Any suggestions?
    Should I just completely undeploy the DbAdapter and redeploy it from the SOA binary installation directory? These are just lab machines right now so that's obviously not a good long term answer for production use but may help start over with refining a better procedure for doing this.

    You should use a non-xa driver for your data source...
    From the weblogic docs...
    Configure Transaction Options
    When you configure a JDBC data source using the Administration Console, WebLogic Server automatically selects specific transaction options based on the type of JDBC driver:
    For XA drivers, the system automatically selects the Two-Phase Commit protocol for global transaction processing.
    For non-XA drivers, local transactions are supported by definition, and WebLogic Server offers the following options ...
    http://docs.oracle.com/cd/E23943_01/web.1111/e13737/jdbc_datasources.htm#autoId8
    Cheers,
    Vlad

  • Oracle post failover transaction commit error

    I have a problem on trasaction after database failover.
    Solaris 8, WLS 6.1 sp3, Oracle 8.1.7 (2 Oracle instances, one is primary and
    another is standby), JDK 1.3.1
    We found this problem in Oracle (Net 8 connection time) failover test.
    Here is what we did.
    During the load, we shut down the primary Oracle server (box).
    All in-flight transactions were wrong, this is ok.
    When new requests came in, WebLogic begin to refresh the connections.
    Because the primary Oracle server was down, it took about 70 seconds to
    refresh a connection (due to the socket timeout value) and redirect to the
    standby Oracle. This is fine.
    After a while, all connections were refreshed and all connected to the
    standby serever.
    When I opened WebLogic console to monitor the in-flight transaction, I found
    some transactions are doing committing and never finished.
    At this time most of the transaction can go through but few of them through
    an exception (attached at the end). This error could never gone although the
    frequency was not high. The strange thing is I checked the database, the
    data was committed.
    I've tried Oracle OCI driver and thin driver, both had this problem. Is
    there anyone can help me on that?
    Thanks,
    Wenji
    <Jan 28, 2003 1:49:57 PM EST> <Error> <EJB> <Exception during commit of
    transaction Name=[EJB
    com.bankframe.bp.retail.solutionset.impl.customersearch.CustomerSearchSessio
    nBean.processDataPacket(com.bankframe.bo.DataPacket)],Xid=28502:685f84a9ba5b
    1ed8(192232),Status=Committing,numRepliesOwedMe=0,numRepliesOwedOthers=0,sec
    onds since begin=122,seconds
    left=60,ServerResourceInfo[weblogic.jdbc.jts.Connection]=(state=ended,assign
    ed=prod-srv2),SCInfo[prod+prod-srv2]=(state=pre-prepared),properties=({weblo
    gic.transaction.name=[EJB
    com.bankframe.bp.retail.solutionset.impl.customersearch.CustomerSearchSessio
    nBean.processDataPacket(com.bankframe.bo.DataPacket)],
    weblogic.jdbc=t3://10.161.46.31:7101}),OwnerTransactionManager=ServerTM[Serv
    erCoordinatorDescriptor=(CoordinatorURL=prod-srv2+10.161.46.31:7101+prod+, R
    esources={})],CoordinatorURL=prod-srv2+10.161.46.31:7101+prod+):
    javax.transaction.SystemException: Timeout during commit processing
    at
    weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTra
    nsactionImpl.java:243)
    at
    weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransaction
    Impl.java:189)
    at weblogic.ejb20.internal.BaseEJBObject.postInvoke(BaseEJBObject.java:272)
    at

    Wenji Tong wrote:
    Thanks, Joe!
    Things could be more complicate. I did some tests to find the details of the
    problem. Here are the results.Hi,
    This is developing into a bigger problem than I can solve informally in newsgroups,
    so I suggest that you open an official support case with this information.
    Joe
    >
    >
    1. I've done a test. In this test, I shut down the Oracle and also stop the
    load. After all threads and connection returned to the pool and all
    transactions done (roll back or abandoned), I started load again. I still
    could find this error. That means this error is not related to any in-flight
    transactions.
    2. After all connectioin failed over, this error was still not gone. The
    frequency was not high, but it was always there.
    3. In WebLogic console, monitor in-flight transaction, I saw some
    transactions were doing committing, but never finished if there was no load.
    When I saw an error printed in log, one of the committing transaction gone
    but there came out another transaction doing the commit and can't be
    finished. I'm not sure if it was related to WebLogic console's bug.
    4. Increase the transaction timeout can fix this problem. Unfortunately, we
    can't increase the transaction timeout anymore due to our business
    requirements.
    I hope those information will be helpful.
    Thanks,
    Wenji
    "Joseph Weinstein" <[email protected]> wrote in message
    news:[email protected]...
    Wenji Tong wrote:
    I have a problem on trasaction after database failover.
    Solaris 8, WLS 6.1 sp3, Oracle 8.1.7 (2 Oracle instances, one is primary
    and
    another is standby), JDK 1.3.1
    We found this problem in Oracle (Net 8 connection time) failover test.
    Here is what we did.
    During the load, we shut down the primary Oracle server (box).
    All in-flight transactions were wrong, this is ok.
    When new requests came in, WebLogic begin to refresh the connections.
    Because the primary Oracle server was down, it took about 70 seconds to
    refresh a connection (due to the socket timeout value) and redirect tothe
    standby Oracle. This is fine.
    After a while, all connections were refreshed and all connected to the
    standby serever.
    When I opened WebLogic console to monitor the in-flight transaction, Ifound
    some transactions are doing committing and never finished.
    At this time most of the transaction can go through but few of themthrough
    an exception (attached at the end). This error could never gone althoughthe
    frequency was not high. The strange thing is I checked the database, the
    data was committed.
    I've tried Oracle OCI driver and thin driver, both had this problem. Is
    there anyone can help me on that?
    Thanks,
    WenjiHi. It seems that Oracle failover is not perfect. Our transactioncoordinator
    is supposed to have control of the transaction. If a failover occurs while
    a transaction is pending, the coordinator should still have the ability toroll
    back the tx. Apparently there are cases where the failover causes an open
    transaction to be committed, in such a way that even if the coordinatorhas
    decided to roll it back, it can't. These may be when the failover occurswhile
    we are waiting for the commit call to return. We either get an exceptionor
    we get no return from the commit() call so we try to roll back and fail.The
    actual commit succeeded, but we never knew.
    Joe
    <Jan 28, 2003 1:49:57 PM EST> <Error> <EJB> <Exception during commit of
    transaction Name=[EJB
    com.bankframe.bp.retail.solutionset.impl.customersearch.CustomerSearchSessio
    >nBean.processDataPacket(com.bankframe.bo.DataPacket)],Xid=28502:685f84a9ba5b
    >1ed8(192232),Status=Committing,numRepliesOwedMe=0,numRepliesOwedOthers=0,sec
    onds since begin=122,seconds
    left=60,ServerResourceInfo[weblogic.jdbc.jts.Connection]=(state=ended,assign
    >ed=prod-srv2),SCInfo[prod+prod-srv2]=(state=pre-prepared),properties=({weblo
    gic.transaction.name=[EJB
    com.bankframe.bp.retail.solutionset.impl.customersearch.CustomerSearchSessio
    nBean.processDataPacket(com.bankframe.bo.DataPacket)],
    weblogic.jdbc=t3://10.161.46.31:7101}),OwnerTransactionManager=ServerTM[Serv
    >erCoordinatorDescriptor=(CoordinatorURL=prod-srv2+10.161.46.31:7101+prod+, R
    esources={})],CoordinatorURL=prod-srv2+10.161.46.31:7101+prod+):
    javax.transaction.SystemException: Timeout during commit processing
    at
    weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTra
    nsactionImpl.java:243)
    at
    weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransaction
    Impl.java:189)
    atweblogic.ejb20.internal.BaseEJBObject.postInvoke(BaseEJBObject.java:272)
    at

  • DB Adapter connecting to DB2 Database is giving Transaction Commit Error

    Hi All,
    I have a simple BPEL process in 11g which executes a select query through the DB adapter in the DB2 database
    The below is the query
    select column1,column2,column3 from table1 where column1='123456'
    During the invoke of the DBAdapter I am getting the following Error in SOAP UI testing tool
    ++<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">++
    ++<env:Header/>++
    ++<env:Body>++
    ++<env:Fault>++
    ++<faultcode>env:Server</faultcode>++
    ++<faultstring>Exception occured when binding was invoked.++
    ++Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'DB2Test' failed due to: DBWriteInteractionSpec Execute Failed Exception.++
    *++unknown failed. Descriptor name: [unknown].++*
    ++Caused by java.sql.SQLException: Cannot call Connection.commit in distributed transaction.  Transaction Manager will commit the resource manager when the distributed transaction is committed..++
    ++".++
    ++The invoked JCA adapter raised a resource exception.++
    ++Please examine the above error message carefully to determine a resolution.</faultstring>++
    ++<faultactor/>++
    ++<detail>++
    ++<exception>Cannot call Connection.commit in distributed transaction.  Transaction Manager will commit the resource manager when the distributed transaction is committed.</exception>++
    ++</detail>++
    ++</env:Fault>++
    ++</env:Body>++
    ++</env:Envelope>++
    The Datasource configured has "Support Global Transactions" option Checked and One Phase Commit selected.
    Any help or pointers in this regard will be greatly appreciated.
    Thanks in advance
    Regards
    Nithya Subramanian

    Hi Anuj,
    I tried the Option 2 given in the thread which you have mentioned.
    Our DataSource is targeted to the managed server so we just restarted the managed server.
    I am still getting the same error of
    "Cannot call Connection.commit in distributed transaction. Transaction Manager will commit the resource manager when the distributed transaction is committed."
    Are there any other alternative approach to fix this issue?
    Regards
    Nithya

Maybe you are looking for

  • Video podcasts are cropped (solution)

    You'll notice that the Ipod nano crops the sides of video podcasts by default. There is a setting to fix this but in order to access it you have to first have a video on your iPod that is not a video podcast. (Apple needs to fix this!!!) To enable th

  • Clarification?: Frank & Lynn's book - task flow "shared" data control scope

    I'm seeking clarification around shared data control scopes please, regarding a point made in Frank Nimphius and Lynn Munsinger's "Oracle Fusion Developer Guide" McGraw-Hill book. On page 229 there is a note that states "The data control scope can be

  • Conflicting files problem when installing wine

    Hi, I'm trying to install wine, but get the following errors. # pacman -S wine resolving dependencies... :: There are 3 providers available for lib32-libgl: :: Repository multilib 1) lib32-mesa-libgl 2) lib32-nvidia-304xx-libgl 3) lib32-nvidia-libgl

  • How did Media Sharing Cable download unknowingly to my MacBook Pro?

    Just recently I discovered a "Media Sharing Cable" software program along with my usual folders (music, pictures, downloads, etc) in my Finder. It says it is an app that was installed before I even purchased my MacBook Pro but I have never noticed it

  • [SOLVED] Quick question about mirrorlist.pacnew

    Is it safe to delete? Does it have to be merged? I may have stupidly made a rash decision after an update to just delete after a quick glance through a wiki about it. Is there a way to view with pacman -Q a chronological order or timeline of recently