Last updated on NOVEMBER 05, 2016
Applies to:Oracle Weblogic Server - Version: 6.1 to 8.1
Information in this document applies to any platform.
The server started and created a access.log0001 and was rotated after n MB (as set), and created a new access.log0002, and then created access.log0003, and so on, up to access.log9999.
When the log file name reached to access.log9999, then the Weblogic Server did not overwrite the access.log0001, and instead started logging in the access.log and without rotating/overwriting anymore. Eventually the access.log file reached to 1GB in size and caused the server to crash.
The files from access.log0001 to access.log4000 were deleted to let WLS create files access.log0001, access.log0002, and so, on.
This issue was confirmed with the below thread.
"ExecuteThread: '59' for queue: 'weblogic.kernel.Default'" daemon prio=5 tid=0x08aae100 nid=0x47 waiting for monitor entry [0x94215000..0x94215d98]
- waiting to lock <0xa0512ec8> (a java.lang.Object)
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