My Oracle Support Banner

Log Files Of Batch Server Are Not Getting Printed Even When 'Log42j.xml' Is Correctly Configured In The System (Doc ID 2592955.1)

Last updated on DECEMBER 18, 2020

Applies to:

Oracle FLEXCUBE Private Banking - Version 12.1.0.0.0 to 12.1.0.0.0 [Release 12]
Information in this document applies to any platform.

Symptoms

ACTUAL BEHAVIOR
----------------------------------------------
Batch Server logs is not getting generated properly even after 'log4j2.xml' file configuration is correct.



EXPECTED BEHAVIOR
----------------------------------------------
Batch Server logs must be generated properly when proper configuration is maintained in 'log4j2.xml' file.

STEPS to reproduce / verify
----------------------------------------------
1. Configure 'log4j2.xml' file properly in the batch server location -> Batch Server home\conf

2. Restart the Batch Server

3. Check whether logs are getting generated successfully.

 


BUSINESS IMPACT
----------------------------------------------
In case if batch server logs are not getting generated properly, troubleshooting of any issue will not be possible since there will be no loggers which can be seen in the console.log file which gets generated. 

This may delay the overall resolution time for SRs which may be related to Mutual Fund Order Management, EOD processing or Document uploads which reside on the Batch Server.

 

 

Changes

There are no changes in the environment, product, account or hardware which has triggered this issue.

 

Cause

To view full details, sign in with your My Oracle Support account.

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


In this Document
Symptoms
Changes
Cause
Solution
References


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