LDAP-Pool-Cleanup-Timer INFO messages logged every 10 minutes in uvserver.log
search cancel

LDAP-Pool-Cleanup-Timer INFO messages logged every 10 minutes in uvserver.log

book

Article ID: 444061

calendar_today

Updated On:

Products

Automic Dollar Universe

Issue/Introduction

After upgrading to Univiewer Management Server (UVMS) 7.01.21, the uvserver.log file records informational messages from the LDAP-Pool-Cleanup-Timer every 10 minutes. This behavior occurs when LDAP synchronization is enabled and can cause log files to grow rapidly.

Symptoms

The following message appears in the uvserver.log every 10 minutes:

 | INFO | LDAP-Pool-Cleanup-Timer | com.orsyp.central.ldap.LDAPPoolCleanupProcess | LDAP Pool Cleanup: Completed successfully (waited 2000ms)

Environment

  • Product: Univiewer Management Server (UVMS)
  • Version: 7.01.21
  • Configuration: LDAP Synchronization Mode enabled (AUTHENTICATION_MODE set to S in values.xml)

Cause

This issue is due to a product defect (DE203812). The LDAPPoolCleanupProcess was introduced to manage thread leaks, but the completion message was incorrectly assigned the INFO log level instead of DEBUG or TRACE.

Resolution

Workaround:

If an immediate fix is required before the release of 7.01.31, contact Technical Support to obtain a modified central.jar for version 7.01.21. This modification changes the log level of the message to DEBUG so it is no longer displayed when the log level is set to INFO.

Solution:

Update to a fix version listed below or a newer version if available.

Fix version(s): 
Component: Univiewer Management Server
Dollar Universe 7.01.31 - planned release November 2026

Additional Information

Public Description: Changed log level from INFO to DEBUG for the LDAP Pool Cleanup process to prevent excessive logging in production environments.

To speak with a customer representative or a Support Engineer, see . Scroll to the bottom of the page and click on your respective region.

It is recommended to subscribe to this article to be updated on the fix status. See .