000036915 - The WildFly server.log file is not updated on RSA Identity Governance & Lifecycle 7.1.0 and above

Document created by RSA Customer Support Employee on Dec 11, 2018Last modified by RSA Customer Support Employee on Oct 16, 2019
Version 6Show Document
  • View in full screen mode

Article Content

Article Number000036915
Applies ToRSA Product Set: Identity Governance & Lifecycle
RSA Version/Condition: 7.1.x
Platform (Other): WildFly

 
IssueAfter installing or upgrading to RSA Identity Governance & Lifecycle version 7.1.0 or above, the WildFly application server log file, /home/oracle/wildfly/standalone/log/server.log, is no longer updated.
 
CauseThe <handler name="FILE"/> entry for the WildFly application server log file is missing from the WildFly application server configuration file,  /home/oracle/wildfly/standalone/configuration/aveksa-standalone-full.xml. Because the file log handler is not configured, the WildFly application server does not log any messages to the WildFly application server log. Only the console log handler is configured in the WildFly configuration file and this information is logged to the application server standard output file, /home/oracle/wildfly/standalone/log/stdout.log. 

This issue has been reported in engineering ticket ACM-92729.
ResolutionThis issue will be resolved in a future release.
 
WorkaroundAs a workaround, add the file log handler (<handler name="FILE"/>)  to the WildFly configuration as shown in the steps below.
  1. Open the /home/oracle/wildfly/standalone/configuration/aveksa-standalone-full.xml in a text editor.
  2. Search for root-logger.
  3. Modify the root-logger configuration:

FROM:



<root-logger>
   <level name="INFO"/>
   <handlers>
      <handler name="CONSOLE"/>
   </handlers>
</root-logger>


TO:



<root-logger>
   <level name="INFO"/>
   <handlers>
      <handler name="FILE"/>
      <handler name="CONSOLE"/>
   </handlers>
</root-logger>


  1. As the oracle user, restart the RSA Identity Governance & Lifecycle service for the change to take effect.


$ acm restart

Attachments

Outcomes