This content has been marked as final.
Show 3 replies
-
1. Re: JTA transaction records not persisted Correctly
marklittle Mar 13, 2008 11:08 AM (in response to dipak_ind2008)OK. And are you using JBoss? This reads like a request for help that would be just as applicable to BEA, Oracle or someone else.
-
2. Re: JTA transaction records not persisted Correctly
dipak_ind2008 Mar 14, 2008 7:07 AM (in response to dipak_ind2008)i am using jboss-4.2.1 GA
i am using oracle databse which is on remote server
i am using the Arjuna transaction api.
i guess it is transaction dealy problem following are my settings :jboss-service.xml:----- <mbean code="com.arjuna.ats.jbossatx.jta.TransactionManagerService" name="jboss:service=TransactionManager"> <attribute name="TransactionTimeout">300</attribute> </mbean>
we have even tried making the timeout value as 3jbossJTA.xml:------- <property name="com.arjuna.ats.arjuna.coordinator.txReaperTimeout" value="120000"/> <!-- Transaction Reaper Mode, can be: NORMAL or DYNAMIC (default is NORMAL). --> <property name="com.arjuna.ats.arjuna.coordinator.txReaperMode" value="NORMAL"/> <!-- (default is NO) --> <property name="com.arjuna.ats.arjuna.coordinator.asyncCommit" value="NO"/> <!-- (default is NO) --> <property name="com.arjuna.ats.arjuna.coordinator.asyncPrepare" value="NO"/>
we have modified the reaper mode as dynamic,
we had also tried setting the reaperTimeout value as 0 and 1200000
we had also tried making asyncCommit and asyncPrepare as true. -
3. Re: JTA transaction records not persisted Correctly
adinn Mar 14, 2008 8:18 AM (in response to dipak_ind2008)
i guess it is transaction dealy problem following are my settings :
You *guess*?
Is there any reason why you made this guess? Are there messages in the logs which say that the reaper has killed your transaction?
Perhaps you should try to switch on debug trace so you can be sure to see what is really happening.