Bug rotate log on startup

[textanalyticsman]

We are using below properties

            WebServer:
                WebServerLog:
                    FileCount: 25
                    # TODO: Below line is not applied, we should check why
                    RotateLogOnStartup: true
                    LogFileFormat: extended

However, we get this

Kindly help us to fix it.

Best regards,
TAM

[CarolynRountree]

can you verify which version of WDT you are using please? Also what version of WebLogic Server?

[CarolynRountree]

I am unable to recreate this using WLS 12.2.1.3

[ddsharpe]

@textanalyticsman I cannot find anything that would cause the behavior that you describe.
If I run

./createDomain.sh -domain_parent . -model_file ./rotateLog.yaml

using the model

domainInfo:
  AdminPassword: welcome1
topology:
  Name: rotatelog
  Server:
    AdminServer:
      WebServer:
        WebServerLog:
          RotateLogOnStartup: true

I get config.xml like:

  <server>
    <name>AdminServer</name>
    <web-server>
      <name>AdminServer</name>
      <web-server-log>
        <name>AdminServer</name>
      </web-server-log>
    </web-server>

The Rotate log file on startup checkbox on the WebLogic Console shows as checked (on/true) for AdminServer -> Logging -> HTTP.

Flipping the value to false in the YAML and repeating the same process:

          RotateLogOnStartup: false

I see the the config.xml looks correct, as well does the console page with the checkbox unchecked (off/false).

  <server>
    <name>AdminServer</name>
    <web-server>
      <name>AdminServer</name>
      <web-server-log>
        <name>AdminServer</name>
        <rotate-log-on-startup>false</rotate-log-on-startup>
      </web-server-log>
    </web-server>

Please reopen this bug if you believe there is still an issue here. For now, I am closing this issue as not reproducible.

[textanalyticsman]

We are still struggling with this issue; we are using WDT 1.9.17. Below you can see a snippet of my WDT model.

AdminServer:
	ServerLifeCycleTimeoutVal: 30
	ListenPort: 9010
	KeyStores: CustomIdentityAndCustomTrust
	CustomIdentityKeyStoreType: jks
	Log:
		FileCount: 25
		LogFileRotationDir: /some/rotate/dir
		LogFileSeverity: Info
		DateFormatPattern: 'yyyy-MM-dd''T''HH:mm:ss.SSSZ'
		MemoryBufferSeverity: Emergency
		DomainLogBroadcastSeverity: Emergency
		StdoutSeverity: Emergency
		FileMinSize: 50000
		RedirectStderrToServerLogEnabled: true
		RedirectStdoutToServerLogEnabled: true
		FileName: '/some/directory/SomeLog.log'
	WebServer:
		WebServerLog:
			FileCount: 25
			RotateLogOnStartup: true
			LogFileFormat: extended
			FileMinSize: 50000

Kindly reopen the case and help us to fix this issue.

[jshum2479]

This looks like a WLST issue. The RotateOnStartup in web server log default is false if in production mode. I see the mbean attribute is correct, the config.xml doesn't show it since default is false, but the console is unchecked.

wls:/offline/sample-domain1/Server/admin-server/WebServer/admin-server/WebServerLog/admin-server>ls()
-rw- NumberOfFilesLimited true
-rw- RotateLogOnStartup true
....

[ddsharpe]

@textanalyticsman I think the issue you are seeing is because the WLS default for RotateLogOnStartup is different depending on if you are running in Production mode or Development mode. When you say "access the console", are you accessing the domain running in Production mode?

[textanalyticsman]

@textanalyticsman I think the issue you are seeing is because the WLS default for RotateLogOnStartup is different depending on if you are running in Production mode or Development mode. When you say "access the console", are you accessing the domain running in Production mode?

The domain has been configured in Production mode.

[jshum2479]

We will have to ask the WLST team to get a patch to get in working.

[ddsharpe]

@textanalyticsman This is a WLST offline bug in WebLogic. The bug is fixed in the next production release of WebLogic Server. To get this fix for the release of WLS that you are using, you will need to file a support case with Oracle technical support and ask that the fix be ported to your specific release. Be sure to mention, in your support case, all one-off patches and PSUs that you are using. The bug number of the original fix is 29547985.