WLS 6.x - <Critical> <JTA>...<Transaction log circular collision, file number ...> - CR128936 (Doc ID 774373.1)

Last updated on NOVEMBER 05, 2016

Applies to:

Oracle Weblogic Server / WebLogic Server / 6.x
Information in this document applies to any platform

Goal

DESCRIPTION:
During regular transactions there appears to be a rare race condition within the tlog file.

       <Nov 20, 2001 3:54:08 PM GMT-06:00> <Notice> <JAM1> <JAM Gateway ready for use.  Current
link status: Up(2)> 
       <Nov 20, 2001 4:02:05 PM GMT-06:00> <Critical> <JTA> <Transaction log circular collision,
file number 2,827> 
       <Nov 20, 2001 4:02:06 PM GMT-06:00> <Critical> <JTA> <Transaction log circular collision,
file number 2,844> 
       <Nov 20, 2001 4:02:07 PM GMT-06:00> <Critical> <JTA> <Transaction log circular collision,
file number 2,861> 
       <Nov 20, 2001 4:02:07 PM GMT-06:00> <Critical> <JTA> <Transaction log circular collision,
file number 2,874>

Now a customer saw one occurrence as:

####<Oct 2, 2003 5:30:54 PM EDT> <Info> <HTTP> <tweek> <dsnTweekProd> <ExecuteThread:
'17' for queue: 'default'> <> <> <101047>
<[WebAppServletContext(2357516,eventreprocess,/eventreprocess)] Generated java file:
/usr/local/bea/wlserver/config/dsn/applications/.wlnotdelete_dsnTweekProd/eventreprocess15528/WEB-INF/_tmp_war_dsn_even
treprocess/jsp_servlet/_dsn_45_docs/_reprocessTool/_networkEvents/__viewer.java> 
####<Nov 20, 2003 5:56:49 PM EST> <Critical> <JTA> <tweek> <dsnTweekProd>
<Thread-0> <> <> <110012> <Transaction log circular collision, file number 3,455>

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms