000035152 - RSA Identity Governance and Lifecycle aveksaServer.log file filling with warning messages "Logging event having message" and "is not logged as queue is full"

Document created by RSA Customer Support Employee on May 22, 2017Last modified by RSA Customer Support Employee on Jun 26, 2017
Version 3Show Document
  • View in full screen mode

Article Content

Article Number000035152
Applies ToRSA Product Set: RSA Identity Governance and Lifecycle
RSA Version: All
IssueThe RSA Identity Governance and Lifecycle aveksaServer.log file is filling up with the following warning messages:
 
11/02/2016 16:45:34.291 WARN (ThreadPool-0) [com.aveksa.server.db.DatabaseAppender] Logging event having message
'Logging event having message 'Logging event having message 'Logging event having message 'Logging event having message
'Logging event having message 'Logging event having message 'Logging event having message 'Logging event having message
'Logging event having message 'Logging event having message 'Logging event having message 'Logging event having message
'Logging event having message 'Logging event having message 'Logging event having message 'Logging event having message
'Logging event having message 'Logging event having message 'Logging event having message 'Logging event having message
'Logging event having message 'Logging event having message 'Logging event having message 'Logging event having

and

is not logged as queue is full' is not logged as queue is full' is not logged as queue is full' is not logged as queue is full'
is not logged as queue is full' is not logged as queue is full' is not logged as queue is full' is not logged as queue is full'
is not logged as queue is full' is not logged as queue is full' is not logged as queue is full' is not logged as queue is full'
CauseInformation logged to the aveksaServer.log is logged both to the physical file and to database table T_AV_APPLICATION_LOG. These errors occur when so much information is being logged to the database that it cannot keep up with the volume of data being logged.
 

Possible causes observed to date


  1. DEBUG logging enabled.  In any environment that has a reasonable amount of load setting, setting the root level logging to DEBUG will cause this error and bring the system to a grinding halt since in addition to logging Aveksa DEBUG statements it will log system level DEBUG including all application server-wide statements.   Root level DEBUG logging should only be used on systems with low usage as a last resort. Instead, use the category log levels. If you have a more specific class level you want to DEBUG, you can use the Advanced tab (usually engineering will provide class specific debugging requirements).
  2. Password Management is enabled, password expiration emails are configured to be sent, and hundreds to thousands of emails are failing to be sent causing exceptional logging activity. 
Resolution

Check that DEBUG is not enabled


  1. If the DEBUG flag under Admin > System > Logs is checked, make sure it is unchecked.
User-added image

  1. If the root logger level under Admin > System > Logs > Settings is enabled, set it to INFO.
User-added image


Password Management Settings


If unchecking the DEBUG flag does not resolve the issue, or if the DEBUG flag is not checked, check your Password Management settings, as follows:
 

  1. Check if Password Management is enabled under Admin > System > Settings.
User-added image

  1. If enabled, check your Password Policy and see if the setting to warn users is enabled. This setting sends an email to users whose passwords are expiring x days before their passwords expire  To do this, select Requests > Password Management > Password Policies tab and click on  the name of the password policy.
 
User-added image

 
  1. Check the email log to see if emails are failing to be sent (Admin > Email > Log tab). Look under Processing Result to see if emails are not being sent.  For example:
User-added image

 

Alternative Solutions


  1. Fix the reason the emails are not being sent (no server defined in the above example), or
  2. Disable the sending of password expired emails, or
  3. Disable Password Management.
WorkaroundIf neither of these scenarios fits your situation, a workaround would be to disable logging altogether on the first page and set root logging level to OFF and contact RSA Identity Governance and Lifecycle Support for a root cause analysis.
 
User-added image
User-added image

Attachments

    Outcomes