search cancel

Tenant disconnect and restart/reload on MSSQL with SSL encryption "Found invalid database connection for local tenant clarity"

book

Article ID: 190033

calendar_today

Updated On:

Products

Clarity PPM On Premise

Issue/Introduction

On MSSQL with SSL encryption and Clarity 15.6:


  1. Error messages in the logs

WARN  2019-12-30 15:59:47,483 [Config Monitor] config.TenantConfigurationManager (none:none:none:none) Found invalid database connection for local tenant clarity

WARN  2019-12-30 15:59:47,702 [Config Monitor] config.TenantConfigurationManager (none:none:none:none) The tenant = clarity has been removed from this Application with instance Id = app :

SYS   2019-12-30 15:59:47,702 [Config Monitor] config.TenantConfigurationManager (none:none:none:none)

ERROR 2019-12-10 23:19:33,196 [ajp-nio-8009-exec-8] filter.RequestTenantIdExtractor (none:none:none:none) 
com.niku.union.config.ConfigurationException: Could not retrieve a valid tenant.

  1. Restarts of BG services with the same messages Found invalid database connection for local tenant clarity AND Could not retrieve a valid tenant.
  2. Reload of the tenants.xml in the app logs
  3. Unable to process request - server error intermittently in Clarity UI, corresponding to this error.

 

Environment

Release : 15.6

Component : CA PPM INTEGRATIONS & INSTALLATIONS

Resolution

Logged as DE53400
We found using the IP address for the database hostname helped on few servers.
 
The issue is environmental as moving the database servers to a new infrastructure helped (using different SSL certificates)