000036915 - WildFly server.log not updated after upgrading to RSA Identity Governance and Lifecycle 7.1.0

Document created by RSA Customer Support Employee on Dec 11, 2018
Version 1Show Document
  • View in full screen mode

Article Content

Article Number000036915
Applies ToRSA Product Set: Identity Governance & Lifecycle
RSA Version/Condition: 7.1.0

 
IssueAfter upgrading to RSA Identity Governance & Lifecycle version 7.1.0, the WildFly application server.log is not updated.
CauseThe <handler name="FILE"/> entry for the WildFly application server log is missing from the WildFly application server configuration file (aveksa-standalone-full.xml). As you can see below, only the console log handler is configured, which will be logged to the application server standard output (stdout.log). As the file log handler is not configured, this causes the WildFly application server not to log any messages to application server log.

The existing aveksa-standalone-full.xml is as follows:

<root-logger>
   <level name="INFO"/>
   <handlers>
      <handler name="CONSOLE"/>
   </handlers>
</root-logger>
ResolutionThis issue has been reported to RSA Engineering (ACM-92729) and is expected to be fixed in a future release.
WorkaroundAs a workaround,
  1. Open the aveksa-standalone-full.xml in a text editor.
  2. Add the <handler name="FILE"/> file log handler as shown below.


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


  1. Restart the RSA Identity Governance & Lifecycle service for the change to take effect.


acm restart

Attachments

    Outcomes