AdminServer.out is of size 0 and nothing is writing to this file rather AdminServer.out00001, 000002 etc files getting created and those are getting written with server logs.
Root cause:
What was found in your setUserOverridesImpl.sh file is that you are
starting the JVM with the parameter : weblogic.RotatingFileRedirector
that is causing the AdminServer.out to be empty.
This is the extract of the setUserOverridesImpl.sh file below:
#Add rotation of out files for weblogic servers
${JAVA_HOME}/bin/java -cp ${MW_HOME}/wlserver/server/lib/weblogic.jar
weblogic.RotatingFileRedirector -configOverride
baseLogFileName=${DOMAIN_HOME}/servers/${SERVER_NAME}/logs/${SERVER_NAME}.out
-config
${MW_HOME}/bi/modules/oracle.bi.sysman/env/stdout_config.properties
&
this bug 30011801 is an Oracle Business Intelligence Enterprise Edition / Analytics System Management bug, not a WebLogic Server defect.
Solution:
Added the below mentioned parameters in stdout_config.properties
numberOfFilesLimited=false
rotationSize=5000
rotatedFileCount=10
baseLogFileName=AdminServer.out
Shutdown Adminserver
Clear all AdminServer.out files
and start the AdminServer
