ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

DX NetOps Portal console service will not start after upgrading to NetOps Performance Management 21.2.9

book

Article ID: 238194

calendar_today

Updated On:

Products

CA Performance Management - Usage and Administration DX NetOps

Issue/Introduction

After the upgrade to 21.2.9 the NetOps Portal console service (caperfcenter_console) will not start.

Starting the service it seems to hang for some time then fails to start.

In the DMService.log can see the following error messages:

WARN  | WrapperSimpleAppMain     | 2022-03-30 11:00:28,141 | org.springframework.web.context.support.XmlWebApplicationContext 
      | Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'statusRS': Cannot create inner bean 'emailjob' of type [com.ca.im.portal.dm.scheduling.email.EmailJobStatusRSImpl] while setting bean property 'serviceBeans' with key [0]; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'emailjob' defined in ServletContext resource [/META-INF/spring/webservices.xml]: Cannot resolve reference to bean 'emailJobScheduler' while setting constructor argument; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'emailJobScheduler' defined in ServletContext resource [/META-INF/spring/email-setup.xml]: Bean instantiation via constructor failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [com.ca.im.portal.dm.scheduling.email.EmailJobScheduler]: Constructor threw exception; nested exception is java.lang.IllegalArgumentException
INFO  | pool-7-thread-1          | 2022-03-30 11:00:28,153 | com.ca.im.portal.dm.productsync.MainPollLoop                     
      | Exiting
ERROR | WrapperSimpleAppMain     | 2022-03-30 11:00:28,157 | org.springframework.web.context.ContextLoader                    
      | Context initialization failed
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'statusRS': Cannot create inner bean 'emailjob' of type [com.ca.im.portal.dm.scheduling.email.EmailJobStatusRSImpl] while setting bean property 'serviceBeans' with key [0]; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'emailjob' defined in ServletContext resource [/META-INF/spring/webservices.xml]: Cannot resolve reference to bean 'emailJobScheduler' while setting constructor argument; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'emailJobScheduler' defined in ServletContext resource [/META-INF/spring/email-setup.xml]: Bean instantiation via constructor failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [com.ca.im.portal.dm.scheduling.email.EmailJobScheduler]: Constructor threw exception; nested exception is java.lang.IllegalArgumentException


These are the same messages seen when upgrading to NetOps Portal 21.2.8, as per this KB article:
https://knowledge.broadcom.com/external/article/236513/dx-netops-portal-console-service-will-no.html

although the values in the general table are already set to the recommended values:

| PDF.Full.Max.Concurrent                    | 1  
| PDF.Max.Concurrent                           | 5                                                           

Cause

Defect DE532185

The setting email_jobs_thread_pool_size is set to a value greater than the default of  5 in file /opt/CA/PerformanceCenter/DM/webapps/dm/WEB-INF/dm.properties

Environment

Release : 21.2.9  

Component : PM Web UI Admininistration/Configuration

Resolution

The following workaround can be used for release 21.2.9:

Check the file /opt/CA/PerformanceCenter/DM/webapps/dm/WEB-INF/dm.properties and verify if the "email_jobs_thread_pool_size" value is set to a higher value than "PDF.Max.Concurrent" value from general table (mysql netqosportal -unetqos -p -e "select * from general where Attribute = 'PDF.Max.Concurrent'").

e.g. 

email_jobs_thread_pool_size = 40

PDF.Max.Concurrent           | 5


If so, do the following and set them to the same value of 5:

1. Edit the file: 
/opt/CA/PerformanceCenter/DM/webapps/dm/WEB-INF/dm.properties

and set:
email_jobs_thread_pool_size = 5

2. Restart the caperfcenter_devicemanager service:
systemctl stop caperfcenter_devicemanager
systemctl start caperfcenter_devicemanager

3. Start the console service:
systemctl start caperfcenter_console

 

 

Additional Information

This has been fixed in NetOps Performance Management 21.2.10

Symptom: Errant setting in the Device Manager configuration with Java upgrade can lead to thread pool exception at start-up time. Excessive values set on customer site for the following email job parameters: email_jobs_thread_pool_size and low_priority_email_jobs_thread_pool_size, can generate error when starting Device Manager.
Resolution: With this fix, the executor initialization now sets the email job parameters when higher than out-of-the-box values, and the device manager starts successfully.
(21.2.10, DE532185, 33072606)