JTA Transaction log circular collision

Question

Greetings:
          Just thought I'd share some knowledge concerning a recent JTA-related
          issue within WebLogic Server 6.1.2.0:
          On our Production cluster, we recently ran into the following critical
          level problem:
          <Jan 10, 2003 6:00:14 PM EST> <Critical> <JTA> <Transaction log
          circular collision, file number 176>
          After numerous discussions with BEA Support, it appears to be a (rare)
          race condition within the tlog file. It was also noted by BEA during
          their testing of WebLogic 7.0.
          Some additional research lead to an MBean attribute under *WebLogic
          Server 7.0* entitled, "CheckpointIntervalSeconds". The documentation
          states:
          ~~~~
          Interval at which the transaction manager creates a new transaction
          log file and checks all old transaction log files to see if they are
          ready to be deleted. Default is 300 seconds (5 minutes); minimum is 10
          seconds; maximum is 1800 seconds (30 minutes).
          Default value = 300
          Minimum = 10
          Maximum = 1800
          Configurable = Yes
          Dynamic = Yes
          MBean class = weblogic.management.configuration.JTAMBean
          MBean attribute = CheckpointIntervalSeconds
          ~~~~
          After searching for a equivalent setting under WebLogic Server
          6.1.2.0, nothing was found and a custom (unsupported) patch was
          created to change this hardcoded setting under 6.1:
          from
          ... CHECKPOINT_THRESHOLD_MILLIS = 5 * 60 * 1000;
          to
          ... CHECKPOINT_THRESHOLD_MILLIS = 10 * 60 * 1000;
          within com.bea.weblogic.transaction.internal.ServerTransactionManagerImpl.
          If you'd like additional details, feel free to contact me via e-mail
          <[email protected]> or by phone [phone]. Hope this
          helps!
          Brian J. Mitchell
          BEA Systems Administrator
          TRX
          6 West Druid Hills Drive
          Atlanta, GA 30329 USA
          

Answer 1

Hi 783703,
As Sridhar suggested for your problem you have to set transaction-time out in j2ee/home/config/transaction-manager.xml.
If you use Idempotent as false for your partnerlinks, BPEL PM will store the status till that invoke(Proof that this invoke gets executed).
So better to go for increasing the time instead of going for idempotent as it has some side effects.
And coming to dehydration ....Ideally performance will be more if there are no much dehydration poitns in our process. But for some scenarios it is better to have dehydration(ex: we can know the status of the process...etc)
Dehydration store will not get cleared after completion of the process. Here dehydration means ....it will store these dtails in tables(like Cube_instance,cube_scope...etc).
Regards
PavanKumar.M