Some of the Logs Defined by Log4j Are Not Generated After Applying RUP for Multiple Times (Doc ID 2398697.1)

Last updated on JANUARY 24, 2024

Applies to:

Symptoms

Actual Behavior

On the environment where RUP was applied for multiple times, setDomainEnv.cmd parameter is updated incorrectly and log4j defined logs (configured in log.xml) such as agile.log, webservice.log is not generated

Expected Behavior

setDomainEnv.cmd parameter to be updated correctly no matter how many RUPs were applied and log4j defined logs such as agile.log, webservice.log to be generated appropriately

Steps

1. On Agile 9.3.6 applied environment, check the logs generated under:
   %Agile_Home%\agileDomain\servers\hostname-Agile\logs
2. Stop Agile Application Server
3. Apply 9.3.6 RUP3
4. Open setDomainEnv.cmd with text editor, and check for below line. This is OK:  
5. Start Agile Application Server from Windows service
6. Check stderr.log. See the error
7. Check logs generated under:
   %Agile_Home%\agileDomain\servers\hostname-Agile\logs, and compare with what you have seen in step 1. See some of the logs such as agile.log, webservices.log are missing

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.