Rollback Issue

I'm trying to put a savepoint and rollback in a when-button-pressed trigger, but it's not working. Can anybody explain me why?
Edited by: 831050 on Jan 25, 2011 7:18 AM

Welcome to the Oracle Forums. Please take a few minutes to review the following:
<ul>
<li>Before posting on this forum please read
<li>10 Commandments for the OTN Forums Member
<li>Announcement: Forums Etiquette / Reward Points
</ul>
The more information you can provide us, the better we will be able to help you. Please give us your Forms version, Client OS version; if web deployed, your Browser and Java versions, a code sample of how you have attempted to create a savepoint and rollback and any error you might be getting.
Craig B-)
If someone's response is helpful or correct, please mark it accordingly.

Similar Messages

Investigate rollback issues

Hi,
How do I get more info on "Perform rollback" issues?
From SM21, I see an ID had "Perform rollback" issue. Double clicking on this entry will display info such as :
"system log message R6 8 : An error has caused an SAP rollback. All database updates will now be reset."
From the trace file (SM50) dev_w0, it shows :
M
M Tue Apr 14 08:30:37 2009
M ***LOG R68=> ThIRollBack, roll back () [thxxhead.c 13168]
There is nothing captured in Oracle alertlog and no short dumps (ST22).
How do I investigate such problems?
Thanks

Hi
Check this forum discussion [Link|http://sap.ittoolbox.com/groups/technical-functional/sap-basis/perform-rollback-233123]
Regards
Uday

Transaction Rollback Issue in SOA Suite

Hi All,
We have been facing the transaction rollback issue very frequently and looking for a concrete solution on this. We have a Asynchronous BPEL process which calls a webservice in a loop of say 20 iteration. In the loop sometimes we face this transaction rollback issue and apparently the CatchAll block doesn't capture this.
In many blogs and oracle metalink we have seen few settings for this and made as per below :
1. JTA Transaction timeout increase : we have it 10000 sec.
2. The Data Source settings : 2.1 : XA transaction timeout check-box selected
2.2 : The Initial Capacity : 10, Maximum Capacity : 200 and Capacity Increment = 5
3. soa-infra -> EJBs -> set the transaction timeout to 1200 for many of the recommended BPELs
4. DISTRIBUTED_LOCK_TIMEOUT = 120 sec.
In short, all the recommended settings are in place. But still, we are facing this issue. Does anyone know if anything is missing in the setting ? Or any other solution to the issue?
Any help is truly appreciated.
Thanks,
Ashwini

I think, even if you change the setting you may not get rid of this problem permanently. Try to avoid call to the webservice in a loop and look for any other alternate solution like JMS (thread should not block for the response of the webservice).

Rollback Issue in BPEL

Hi All,
I am facing issue with Txn rollback in BPEL while using fault policies.My BPEL polls JMS Q and invokes 2 databases and 1 jms adapter in a sequential manner. I want if any invocation fails , the preceding successful invocations should be rollbacked and txn should be retried as per the source jms q retry settings .I have worked on it using 2 approaches-
1. Without using Fault Policy- I created a catchall and added a throw activity with rollback fault in it. So if any invocation fails, the rollback and retry is working fine as per the source Q retry settings.
2.With Fault Policy- I created a fault policy and fault binding(composite/reference level).Also I created a catchall and added a throw activity with rollback fault in it.When any invocation fails, the fault policy is called, and the Ora:retry action executes and retry calling the failed adapter as per the retry configuration set in the policy file. If after all retries, still invocation fails, then transaction goes to CatchAll block.Here is the problem.The transaction is not getting rollbacked and does not even retry as per the JMS Q retry configuration.
My agenda is to have a process, where in if any invocation fails, that should be retried as per fault policy retry configuration.If still invocation is faulted after all retries, the preceding invocations should be rollbacked and the message should be rollbacked to source jms Q. Again bpel should be instantiated with new transaction. Each instance should itself retry as per fault policy retry configuration.It should keep on retrying(creating new instances) till source Q jms retry limit is achieved.
Please help..
Thanks
Rishu

Hi Ananth,
Thanks for your reply.
I am using fault policies for Error handling in all my interfaces instead of handling the faults using the catch block.So the same approach I need to follow in this interface as well , where I am facing the issue. In my affected interface, I have 3 invocations in sequence manner and want that If any invocation fails, the earlier successful transactions should be rollbacked.So when I am using fault policy, the failed invocation is getting retried as per the fault policy retry , but it is not rollbacking the earlier 2 successful invocations, which it should do to have an effective error handling. Same is getting accomplished by using Catch and throwing rollback error from there. I am ok even if Q retry should not get executed but I need to rollback the previous successfully executed invocations.Could you please let me know how to handle this scenario using fault policy..May be I am skipping something then..
Thanks and Regards,
Rishu Sharma

Photoshop Elements 9 'Rollback Issue'?

Everytime I try to install Photostop Elements 9, it finishes installing, and just when it starts registering the product, it fails and has to rollback, and the program is uninstalled. Im running Windows 7 Home Premium 64 Bit.
Can anyone help or suggest something I do?

OMG...I have been dealing with this issue ALL day and it is now 11:51 pm!!! I had purchased a new, sealed, PSE 9 on dvd, tried to install it...almost got to the end and it started rolling back. got the same screen about the Installshield. Spent hours researching a fix on the internet...nothing worked. Finally found and let an Adobe tech take control of my computer. He tried a couple of different things but the rollback continued. Then he tried to make another administrator account (I'm on XP media edition) and he hit restart...and was gone. Then I had to spend a couple hours trying to get my settings and configurations back to the way they were (for some reason the computer reverted to the programs and setting it originally came with and system restore wouldn't work)
Finally got things back to how they were, went on to Adobe and purchased a download copy of PSE 9 from their store. More money again but I thought if it works I really don't care. All excited and spent the time downloading the program, went to install it, and same darn rolling back problem. Tried a couple more times in disbelief...no change.
Then did research into more Installshield problems and possible fixes and then updates, patches, drivers and finally researched reinstall. Found it finally on c-net, downloaded and reinstalled Installshield (it copied, replaced, fixed, cleaned etc as I watched). Excitedly I tried to install the downloaded copy of PSE 9...but the rolling back continues!!!!!!!!
I have NEVER had this problem with installing software before (downloaded or hard copies). Please please please someone figure this out!!!!!!!!!!!!!!
Thanks,
Linda

WebLogicJtaTransactionManager rollback issue

Hi All,
I have some problem using WebLogicJtaTransactionManager. My problem is although there is an exception, the transaction cannot rollback.
I'm using hibernate + spring and weblogic as the application server.
this is my code:
<?xml version="1.0" encoding="UTF-8"?>
<beans xmlns="http://www.springframework.org/schema/beans"
     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
     xmlns:tx="http://www.springframework.org/schema/tx"
     xmlns:aop="http://www.springframework.org/schema/aop"
     xmlns:jee="http://www.springframework.org/schema/jee"
     xsi:schemaLocation="
          http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-2.0.xsd
          http://www.springframework.org/schema/tx http://www.springframework.org/schema/tx/spring-tx-2.0.xsd
          http://www.springframework.org/schema/aop http://www.springframework.org/schema/aop/spring-aop-2.0.xsd
          http://www.springframework.org/schema/jee http://www.springframework.org/schema/jee/spring-jee.xsd">
     <jee:jndi-lookup id="dataSource" jndi-name="localDS" />
     <jee:jndi-lookup id="myNetsDataSource" jndi-name="myNetsDS" />
     <bean id="sessionFactory"
          class="org.springframework.orm.hibernate3.LocalSessionFactoryBean" destroy-method="destroy">
          <property name="dataSource" ref="dataSource" />
          <property name="configurationClass">
               <value>org.hibernate.cfg.AnnotationConfiguration</value>
          </property>
          <property name="configLocations">
               <list>
                    <value>/WEB-INF/hibernate.cfg.xml</value>
               </list>
          </property>
          <property name="hibernateProperties">
               <props>
                    <prop key="hibernate.connection.driver_class">${hibernate.connection.driver_class}</prop>
                    <prop key="hibernate.dialect">${hibernate.dialect}</prop>
                    <prop key="hibernate.current_session_context_class">${hibernate.current_session_context_class}</prop>
                    <prop key="hibernate.show_sql">${hibernate.show_sql}</prop>
                    <prop key="hibernate.format_sql">${hibernate.format_sql}</prop>
               </props>
          </property>
     </bean>
     <bean id="myNetsSessionFactory"
          class="org.springframework.orm.hibernate3.LocalSessionFactoryBean" destroy-method="destroy">
          <property name="dataSource" ref="myNetsDataSource" />
          <property name="configurationClass">
               <value>org.hibernate.cfg.AnnotationConfiguration</value>
          </property>
          <property name="configLocations">
               <list>
                    <value>/WEB-INF/myNets-hibernate.cfg.xml</value>
               </list>
          </property>
          <property name="hibernateProperties">
               <props>
                    <prop key="hibernate.connection.driver_class">${hibernate.connection.driver_class}</prop>
                    <prop key="hibernate.dialect">${hibernate.dialect}</prop>
                    <prop key="hibernate.current_session_context_class">${hibernate.current_session_context_class}</prop>
                    <prop key="hibernate.show_sql">${hibernate.show_sql}</prop>
                    <prop key="hibernate.format_sql">${hibernate.format_sql}</prop>
               </props>
          </property>
     </bean>
     <bean id="txManager"
          class="org.springframework.transaction.jta.WebLogicJtaTransactionManager">
          <property name="transactionManagerName"
value="javax.transaction.TransactionManager"/>
     </bean>
     <aop:config>
          <aop:pointcut
               expression="execution(* com.kiosk.commonlib.service.*.*(..))"
               id="ats" />
          <aop:advisor advice-ref="txAdvice" pointcut-ref="ats" />
     </aop:config>
          <tx:advice id="txAdvice" transaction-manager="txManager">
          <tx:attributes>
               <tx:method name="save*" propagation="REQUIRED" />
               <tx:method name="delete*" propagation="REQUIRED" />
               <tx:method name="remove*" propagation="REQUIRED" />
               <tx:method name="update*" propagation="REQUIRED" />
               <tx:method name="log*" propagation="REQUIRED" />
               <tx:method name="get*" propagation="REQUIRED"
                    read-only="true" />
               <tx:method name="list*" propagation="REQUIRED"
                    read-only="true" />
          </tx:attributes>
          </tx:advice>
</beans>
I created two datasource (localDS and myNetsDS) in weblogic server, both access to different database. is there something wrong with my txmanager configuration?
Thanks

Hi Ananth,
Thanks for your reply.
I am using fault policies for Error handling in all my interfaces instead of handling the faults using the catch block.So the same approach I need to follow in this interface as well , where I am facing the issue. In my affected interface, I have 3 invocations in sequence manner and want that If any invocation fails, the earlier successful transactions should be rollbacked.So when I am using fault policy, the failed invocation is getting retried as per the fault policy retry , but it is not rollbacking the earlier 2 successful invocations, which it should do to have an effective error handling. Same is getting accomplished by using Catch and throwing rollback error from there. I am ok even if Q retry should not get executed but I need to rollback the previous successfully executed invocations.Could you please let me know how to handle this scenario using fault policy..May be I am skipping something then..
Thanks and Regards,
Rishu Sharma

DB Adapter rollback issue

Hi All,
We have a DB Adapter in our BPEL message flow to insert records to target DB and in case of error while invoking DB Adapter we are catching the error in catch and catch all block.
But in some scenarios like when we pass value of larger size to columns than what is declared in table( eg: if we pass 'YES' to column which datatype and size is varchar2(1)) then error is not caught in catch or catch all block, instead the process is getting rolled back with below exception.
We have tried with both XA connection and also non-XA connection but still the same issue. We have also set the JTA timeout to "2400". Could you please help us on this ?
Thanks in advance
<exception class="com.collaxa.cube.engine.EngineException">
JTA transaction is not in active state. The transaction became inactive when executing activity "" for instance "460,011", bpel engine can not proceed further without an active transaction. please debug the invoked subsystem on why the transaction is not in active status. the transaction status is "MARKED_ROLLBACK". The reason was The execution of this instance "460011" for process "MSITesseractDBInsert" is supposed to be in an active jta transaction, the current transaction status is "MARKED_ROLLBACK", the underlying exception is "BINDING.JCA-12563 Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'insert' failed due to: DBWriteInteractionSpec Execute Failed Exception. insert failed. Descriptor name: [InsertCustomerDataToTesseractDB.MotCustomerLoadIn]. Caused by java.sql.BatchUpdateException: String or binary data would be truncated.. Please see the logs for the full DBAdapter logging output prior to this exception. This exception is considered not retriable, likely due to a modelling mistake. To classify it as retriable instead add property nonRetriableErrorCodes with value "-8152" to your deployment descriptor (i.e. weblogic-ra.xml). To auto retry a retriable fault set these composite.xml properties for this invoke: jca.retry.interval, jca.retry.count, and jca.retry.backoff. All properties are integers. ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution. " . Consult the system administrator regarding this error.
<stack>
<f>com.oracle.bpel.client.util.TransactionUtils.throwExceptionIfTxnNotActive#107</f>
<f>com.collaxa.cube.ws.WSInvocationManager.invoke#352</f>
<f>com.collaxa.cube.engine.ext.common.InvokeHandler.__invoke#1070</f>
<f>com.collaxa.cube.engine.ext.common.InvokeHandler.handleNormalInvoke#584</f>
<f>com.collaxa.cube.engine.ext.common.InvokeHandler.handle#132</f>
<f>com.collaxa.cube.engine.ext.bpel.common.wmp.BPELInvokeWMP.__executeStatements#74</f>
<f>com.collaxa.cube.engine.ext.bpel.common.wmp.BaseBPELActivityWMP.perform#166</f>
<f>com.collaxa.cube.engine.CubeEngine.performActivity#2687</f>
<f>com.collaxa.cube.engine.CubeEngine._handleWorkItem#1190</f>
<f>com.collaxa.cube.engine.CubeEngine.handleWorkItem#1093</f>
<f>com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handleLocal#76</f>
<f>com.collaxa.cube.engine.dispatch.DispatchHelper.handleLocalMessage#218</f>
<f>com.collaxa.cube.engine.dispatch.DispatchHelper.sendMemory#297</f>
<f>com.collaxa.cube.engine.CubeEngine.endRequest#4609</f>
<f>com.collaxa.cube.engine.CubeEngine.endRequest#4540</f>
<f>com.collaxa.cube.engine.CubeEngine._createAndInvoke#713</f>
<f>...</f>
</stack>Regards,
Ramesh
Edited by: Ramesh Menon on Mar 7, 2013 1:12 PM

Hi All,
We have a DB Adapter in our BPEL message flow to insert records to target DB and in case of error while invoking DB Adapter we are catching the error in catch and catch all block.
But in some scenarios like when we pass value of larger size to columns than what is declared in table( eg: if we pass 'YES' to column which datatype and size is varchar2(1)) then error is not caught in catch or catch all block, instead the process is getting rolled back with below exception.
We have tried with both XA connection and also non-XA connection but still the same issue. We have also set the JTA timeout to "2400". Could you please help us on this ?
Thanks in advance
<exception class="com.collaxa.cube.engine.EngineException">
JTA transaction is not in active state. The transaction became inactive when executing activity "" for instance "460,011", bpel engine can not proceed further without an active transaction. please debug the invoked subsystem on why the transaction is not in active status. the transaction status is "MARKED_ROLLBACK". The reason was The execution of this instance "460011" for process "MSITesseractDBInsert" is supposed to be in an active jta transaction, the current transaction status is "MARKED_ROLLBACK", the underlying exception is "BINDING.JCA-12563 Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'insert' failed due to: DBWriteInteractionSpec Execute Failed Exception. insert failed. Descriptor name: [InsertCustomerDataToTesseractDB.MotCustomerLoadIn]. Caused by java.sql.BatchUpdateException: String or binary data would be truncated.. Please see the logs for the full DBAdapter logging output prior to this exception. This exception is considered not retriable, likely due to a modelling mistake. To classify it as retriable instead add property nonRetriableErrorCodes with value "-8152" to your deployment descriptor (i.e. weblogic-ra.xml). To auto retry a retriable fault set these composite.xml properties for this invoke: jca.retry.interval, jca.retry.count, and jca.retry.backoff. All properties are integers. ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution. " . Consult the system administrator regarding this error.
<stack>
<f>com.oracle.bpel.client.util.TransactionUtils.throwExceptionIfTxnNotActive#107</f>
<f>com.collaxa.cube.ws.WSInvocationManager.invoke#352</f>
<f>com.collaxa.cube.engine.ext.common.InvokeHandler.__invoke#1070</f>
<f>com.collaxa.cube.engine.ext.common.InvokeHandler.handleNormalInvoke#584</f>
<f>com.collaxa.cube.engine.ext.common.InvokeHandler.handle#132</f>
<f>com.collaxa.cube.engine.ext.bpel.common.wmp.BPELInvokeWMP.__executeStatements#74</f>
<f>com.collaxa.cube.engine.ext.bpel.common.wmp.BaseBPELActivityWMP.perform#166</f>
<f>com.collaxa.cube.engine.CubeEngine.performActivity#2687</f>
<f>com.collaxa.cube.engine.CubeEngine._handleWorkItem#1190</f>
<f>com.collaxa.cube.engine.CubeEngine.handleWorkItem#1093</f>
<f>com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handleLocal#76</f>
<f>com.collaxa.cube.engine.dispatch.DispatchHelper.handleLocalMessage#218</f>
<f>com.collaxa.cube.engine.dispatch.DispatchHelper.sendMemory#297</f>
<f>com.collaxa.cube.engine.CubeEngine.endRequest#4609</f>
<f>com.collaxa.cube.engine.CubeEngine.endRequest#4540</f>
<f>com.collaxa.cube.engine.CubeEngine._createAndInvoke#713</f>
<f>...</f>
</stack>Regards,
Ramesh
Edited by: Ramesh Menon on Mar 7, 2013 1:12 PM

Apple Mobile Device Support will not install! Any answers re rollback issue?

Hi,
Im running Windows 32bit and trying to install the latest Itunes version 10.5.1.42 after a few attempts i have managed to install all of it apart form Application Modbile Device Support (AMDS), therefore meaning that i can not sync with my new Iphone.
Essentialy when it gets to installing AMDS it rolbacks. It can create the folders ok and but does not copy any drivers into the folders. All the other Apple folders in common files directory are ok and populated and work. I tunes work - just doesnt let me connect my phone as AMDS is empty.
I have noticed a few threads regarding this issue over the years and tried lots of the suggestions:
completely uninstalling Itunes and all traces of associated apple products. Manually removing residual files. Done this lots and lots of times, Itunes etc will install, AMDS will not
checked various permissions
Ensured Windows updates are all up to date
Removed other mobile phone software
changed msconfig settings
Im just going around in circles now. I cant bear the thought of running thorugh another uninstall of Itunes and ten watching it install again only to see the roll back bar appear and reverse!
Any idea people?

For general advice see Troubleshooting issues with iTunes for Windows updates.
The steps in the second box are a guide to removing everything related to iTunes and then rebuilding it, which is often a good starting point unless the symptoms indicate a more specific approach. Review the other boxes and the list of support documents further down page in case one of them applies.
Your library should be unaffected by these steps but there is backup and recovery advice elsewhere in the user tip.
The section Install missing components has advice on breaking down the iTunes installer into the individual .msi files which might prove useful if one component, such as Apple Mobile Device Support, won't install normally.
In your case I suggest you start with a clean download of the setup file using the direct link. If reinstalling AMDS alone doesn't work try tearing everything down again.
If that fails try the advice on rolling back to the last build of iTunes that worked for you.
tt2

Having installation rollback issues with PSE 9?

Mr. Ankush Ved helped to solve my PSE 9 installation issues in under 30 mins! Well
done Ankush. There was a cache file conflict that needed resolution. I recommend you contact Ankush via private message here, provide him with your email address and allow him to see and operate your computer remotely.
Adobe tech support (phone) was no help last night and I was on with them for over 1.5 hours!
Somebody please give Mr. Ved a raise!

LOL....
Thanks to you for your patience and confidence. Glad that I was able to help you.
Best Regards,
Ankush

DB Transaction ROLLBACK issues

Hi All,
I am running BPEL version 10.1.2.0.2, and i am trying out DB Transactional Insert. It looks like it is not doing proper rollback when an exception is occuring in BPEL process flow as well as the audit trace is also not generated when an exception happens. Is this a bug in this version and is there a patch available.
I have set the property in bpel.xml as transaction=participate and in partner link participate=true. For Transactionality is there any other setting to be done in any config xml files like /../../data-source.xml or oc4j-ra.xml
Appreciate if any one can let me know if i need to do any other settings
Thank you
RM

According to Clemens at his note:
there are some consideration for making this happen ..
a) process type should be sync (to ensure the process runs in one thread)
b) on each partnerlink specify participate=true (as property) and
c) db adapter's database connection MUST point to a XA-location to participate in the global tx ..
Re: the transaction on multiple PL/SQL Web Service on once BPEL process

Windows 8 Rollback issue or Security issue

I think I may have made a mistake in trying to reset my computer. I had some viral activity that had taken over my Norton security and was messing with my computer. I tried to fix it but Norton became too corrupted and could not recognize any virus. I
have an HP Envy that is about a year old and I had updated it to Windows 8.1 when I had internet. My wife had her computer crash on her several months back and to save her data I just copied her entire hardrive onto the extra hard drive that I had installed.
I did not think to much of it but when I had some issues with my computer and did a system refresh on my computer I think it found the files and is getting the 2 system files confused. I also purchased a copy of office 2010 from a source on the internet that
said I had to uninstall all other versions because the key they had would not work with trial versions. Little afraid that it is bootlegged. now my computer is acting funny. I do not have access to all files on it and I have programs that are running and migrating
so not sure what to do. Any advice?????

Hello,
Sorry for the trouble. I am Vineeth and I am from the Norton Support team.
Did you try reinstalling the Norton product? Can you run a scan with the free Norton Power Eraser tool and see if it detects any problems: http://www.Norton.com/npe?
Thanks!
Vineeth
Norton Support

JMS Message Rollback Issue.

Hi,
I have a requirement where i have to read from a queue and then insert into a table. There are 2 scenarios where the message should remain in the queue
a) If the insert fails
b) There is some exception after reading the message but before inserting into the table.
I am using Weblogic, Oracle and MQ Series
I have created the QCF (XA based) and also created a XAdatasource thru the WL console.
However, the XA does not seem to be happening!!
This is my spring configuration
<bean id="TxManager" class="org.springframework.transaction.jta.WebLogicJtaTransactionManager" >
<property name="jndiTemplate" ref="jndiTemplate"></property>
<property name="transactionManagerName" value="javax.transaction.TransactionManager"/>
</bean>

<aop:config proxy-target-class="true">
<aop:advisor pointcut="execution(* *..*Processor*.*(..))" advice-ref="txReqAdvice"/>
<aop:advisor pointcut="execution(* *..*Listener*.*(..))" advice-ref="txReqAdvice" />
<aop:advisor pointcut="execution(* *..*Dao*.*(..))" advice-ref="txReqAdvice"/>
</aop:config>
<aop:config />
<tx:advice id="txReqAdvice" transaction-manager="TxManager">
<tx:attributes>
<tx:method name="save*" propagation="REQUIRED" timeout="100"/>
<tx:method name="on*" propagation="REQUIRES_NEW" timeout="100" />

</tx:attributes>
</tx:advice>
<tx:advice id="txReqNewAdvice" transaction-manager="TxManager">
<tx:attributes>
<tx:method name="create*" read-only="false" propagation="REQUIRES_NEW" />
<tx:method name="update*" read-only="false" propagation="REQUIRES_NEW"/>
<tx:method name="insert*" read-only="false" propagation="REQUIRES_NEW"/>
<tx:method name="add*" read-only="false" propagation="REQUIRES_NEW"/>
<tx:method name="*" propagation="REQUIRED"/>
</tx:attributes>
</tx:advice>


<bean id="jndiTemplate"
class="org.springframework.jndi.JndiTemplate">
<property name="environment">
<props>
<prop key="java.naming.factory.initial">weblogic.jndi.WLInitialContextFactory</prop>
<prop key="java.naming.provider.url">t3://localhost:7001</prop>
</props>
</property>
</bean>

<bean id="jmsQueueConnectionFactory"
class="org.springframework.jndi.JndiObjectFactoryBean">
<property name="jndiTemplate" ref="jndiTemplate">
</property>
<property name="jndiName" value="/jms/WLReceiverQCF">
</property>
<property name="lookupOnStartup" value="false"/>
<property name="proxyInterface" value="javax.jms.QueueConnectionFactory"/>
</bean>
<bean id="jmsXAQueueConnectionFactory"
class="org.springframework.jndi.JndiObjectFactoryBean">
<property name="jndiTemplate" ref="jndiTemplate">
</property>
<property name="jndiName" value="/jms/WLXAReceiverQCF">
</property>
<property name="lookupOnStartup" value="false"/>
<property name="proxyInterface" value="javax.jms.XAQueueConnectionFactory"/>
</bean>



<bean id="destinationQueue"
class="org.springframework.jndi.JndiObjectFactoryBean">
<property name="jndiTemplate">
<ref bean="jndiTemplate" />
</property>
<property name="jndiName">
<value>/jms/WLReceiverQueue</value>
</property>
<property name="proxyInterface" value="javax.jms.Queue"/>
</bean>
<bean id="jmsQueueTemplate"
class="org.springframework.jms.core.JmsTemplate102">
<property name="connectionFactory" ref="jmsQueueConnectionFactory">
</property>
<property name="defaultDestinationName" value="RequestQQ"/>



</bean>
<bean id="jmsSender" class="com.sample.JmsSender">
<property name="jmsTemplate102">
<ref bean="jmsQueueTemplate"/>
</property>
</bean>
<bean id="jmsListener"
class="com.sample.JMSRequestListener" />
<bean id="jmsListenerContainer"
class="org.springframework.jms.listener.DefaultMessageListenerContainer">
<property name="connectionFactory" ref="jmsXAQueueConnectionFactory" />
<property name="destinationName" value="RequestQQ" />
<property name="messageListener" ref="jmsListener" />
<property name="transactionManager" ref="TxManager" />
<property name="transactionTimeout" value="100" />

</bean>
<bean id="datasource"
class="org.springframework.jndi.JndiObjectFactoryBean">
<property name="jndiTemplate" ref="jndiTemplate"/>
<property name="jndiName">
<value>jdbc/MyDS</value>
</property>
<property name="expectedType" value="javax.sql.DataSource"/>
<property name="lookupOnStartup" value="false"/>
</bean>
<bean id="hibernatePropsBean" class="org.springframework.beans.factory.config.PropertiesFactoryBean">
<property name="properties">
<props>
<prop key="hibernate.dialect">org.hibernate.dialect.OracleDialect</prop>
<prop key="hibernate.default_schema">common</prop>
<prop key="hibernate.show_sql">true</prop>
<prop key="hibernate.cache.provider_class">org.hibernate.cache.NoCacheProvider</prop>
<prop key="hibernate.connection.release_mode">after_transaction</prop>
</props>
</property>
</bean>
<bean id="sessionFactory" class="org.springframework.orm.hibernate3.LocalSessionFactoryBean">

<property name="dataSource" ref="datasource"/>
<property name="hibernateProperties" ref="hibernatePropsBean"/>
<property name="mappingResources">
<list>
<value>com/sample/Event.hbm.xml</value>
</list>
</property>
</bean>
<bean id="EventDAO" class="com.sample.EventSpringDao">
<property name="sessionFactory" ref="sessionFactory"/>
</bean>
</beans>
Can somebody point me where i am doing a mistake?
Regards
Siva.

Ensure that the custom connection factory with JNDI name "/jms/WLXAReceiverQCF" is configured with "XA Transactions Enabled".
Try setting the Spring "sessionTransacted" to "false" -- which should be the default. googling "Spring sessionTransacted" reveals there's a bit of weirdness with this field, and behavior may differ with different JMS vendors.
FWIW For a variety of reasons, including your plans to use MQSeries XA, I would normally recommend using WebLogic MDBs rather than the Spring messaging container.
Tom

Rollback issue urgent tips needed

I am dealing with two tables say A and B
table A is a live production data table
and table B is a global temporary table
The real case scene is that under some conditions some rows n table (A) (prod table) r modified but not commited
later an insert takes place on table (B) and those rows from table A which were updated may also get inserted depending on insert conditions specified
Now the problem is that if the application is killed (via some client terminal) then the commit is performed on table (A) which is prod table and is not supposed to be commited
also table A and table B have different attributes and
final report is generated depending on table(B)
columns of table(A) and table (B) are different with no attribute that is unique and common between them
below are structures of table(A) and table (B)
TABLE A TABLE B
DEFECT_LOG_ID
AREA_ID_FOUND
TRACK_ID
DEFECT_DATETIME
DEFECT_CODE
PERSONNEL_ID
STATUS_CODE
REF_DES
AREA_ID_CHARGED
STATION_CHARGED
FEEDER
NOZZLE
TEST_LINK_ID
TABLE B
PROD_FAMILY_ID
PART_NU
VER_CODE
REF_DES
DEFECT_DESC
QUANTITY
CHARGED
PERSONNEL_ID
TEST_TYPE
AREA_ID
STATUS_CODE
MEASURE_CODE
suggest a way so that we dont have to do update production table (A)
(so tht undesired commit does not take place)
but the updated values are available to temporary table (B)
one way i thought was to introduce a new column in temporary table (B) which is PK of table (A) (but then the update query that updated table (A) will have to be changed as columns in both tables are different )
or introduce a duplicate temporary table of table (A) and do updations on it instead of table (A)

What does 'application is killed' mean?
Does it imply that some one closed the application (using the appropriate menu or clicking on the 'X' box) or used Windows Task Manager to kill it?
Does it imply that some one killed the database connection?

Issue with Payables Accounting Process

I have an issue right now with Payables Accounting Process. Is says:
Oracle Payables: Version : 11.5.0 - Development
Copyright (c) 1979, 1999, Oracle Corporation. All rights reserved.
APACCENG module: Payables Accounting Process
Current system time is 25-AUG-2009 13:23:41
+-----------------------------
| Starting concurrent program execution...
+-----------------------------
Arguments
P_START_DATE='2009/08/02 00:00:00'
P_END_DATE='2009/08/23 00:00:00'
P_JOURNAL_CATEGORY='All'
P_SUB_TRANSF_TO_GL='N'
P_SUB_JOURNAL_IMP='N'
P_VALIDATE_ACCTS='Y'
P_SUMMARIZE_FLAG='N'
P_COMMIT_CYCLE='50'
P_ORG_ID='81'
P_DEBUG_SWITCH='N'
P_TRACE_SWITCH='N'
P_RUN_ACCT_REPORT='N'
APPLLCSP Environment Variable set to :
Current NLS_LANG Environment Variable is :
American_America.UTF8
MSG-00002: Check that AX is not installed before calling the accounting engine
MSG-00003: AX is not installed, Calling the accounting engine
MSG-00004: After the call to AP_Accounting_Engine_Pkg.Do_Accounting
MSG-00005: Error occured in the accounting process
MSG-00006: Error Message: ORA-20100: File o0002869.tmp creation for FND_FILE failed.
You will find more information on the cause of the error in request log. occurred in
&CALLING_SEQUENCE
with parameters (&PARAMETERS)
while performing the following operation:
&DEBUG_INFO
REP-1419: 'beforereport': PL/SQL program aborted.
Report Builder: Release 6.0.8.20.2 - Production on Tue Aug 25 13:23:41 2009
(c) Copyright 1999 Oracle Corporation. All rights reserved.
Enter Username:
Program exited with status 1
Concurrent Manager encountered an error while running Oracle*Report for your concurrent request 820318.
Review your concurrent request log and/or report output file for more detailed information.
Executing request completion options...
Output is not being printed because:
The print option has been disabled for this report.
Finished executing request completion options.
Concurrent request completed
Current system time is 25-AUG-2009 13:23:43
I had a similar issue writing to the UTL_FILE_DIR with the AR Interface and was able to resolve that by checking the read/write permissions on the UTL_FILE_DIR sat in the init.ora. However, the strange thing here is I still get the same error for Payables Accounting Process.
Any insights would be greatly appreciated.
Thanks,
Don

This issue has been resolved. But the solution for me was totally unrelated to the error message that came up with this issue.
We had rollback issues in average and layer cost worker under Bills of Material. And after applying patch 3325415, this issue was also resolved.
This issue has been answered but if anyone has any ideas on how this issue got resolved by patch 3325415, i'd like to understand.
Thanks,
Don

Perfroming RollBack() For DML's

Hi
I have a sessionBean with CMT. The following is the method with Required Attribute in Bean:
method A()
try
     //call proc & Create Table T1
     //call proc & Create Table T2
     //Perform Insert in Table T3
     //Perform Insert in Table T4 -- This throws some kind of Exception e.g. SQLException
catch(ApplicationLevelException e)
     sessionContext.setRollbackOnly();// to rollBack the inserts
     //call proc for Dropping the Tables created above
     throw e;// to rollBack()
catch(SQLException e)
     // call proc for Dropping the Tables created above
     throw new EJBException();// to rollBack()
}// end method A()
Whenever any DML Statement is executed, it will implicitly commit all the previous DML's, if any. e.g. Inserts
Hence, the problem with above is that once you call procedure for dropping Tables (which is considered as a DML) , it will automatically commit the Insert in Table T3.
Is there any way in which I can perform RollkBack() for Insert in T3 and also Drop the tables T1 and T2?
Thanks.

No.
Thats what my Bean is suppose to do.
Create required Tables and Perform Inserts.
In our scenario, you can assume that it wont be a costly operation.
Back to the RollBack() issue, one thing that comes to my mind is when i call the DropTbl() procedure, the first thing it shud do it is : rollBack(). So, that it rolls back all the previous Inserts. And then it can go on Dropping created Tables.
Is there any other way anyone suggest?

Rollback Issue

Similar Messages

Maybe you are looking for