Disabled Notification entry does not show in UI consistently

Document ID : KB000100330
Last Modified Date : 06/06/2018
Show Technical Document Details
Issue:
Created a new Notification entry set to Disabled.

It appears "randomly" when going to the the "Manage Notifications" page.

Hitting the Refresh button at the page or browser tab level returns similar results. Sometimes it appears and sometimes it does not.
Environment:
All supported CA Performance Management releases
Cause:
Reconfigured ports during attempt at custom SSL and port configurations caused sync problems between the CA Performance Center Console (caperfcenter_console), Device Manager (caperfcenter_devicemanager) and Event Manager (caperfcenter_eventmanager) services. 

Due to this the Notifications, synced from console->devicemanager->eventmanager and back again, were not being consistently returned to the web server console service requests. 

This is observed in first this error that was resolved: 
ERROR | pool-1-thread-256 | 2018-05-10 17:19:23,885 | com.ca.im.portal.em.ds.EventProducerPoller 
| PollEventProducers 
javax.xml.ws.WebServiceException: Could not send Message. 
Caused by: java.net.ConnectException: ConnectException invoking https://138.193.232.13:8182/pc/center/eventProducerWS: Connection refused (Connection refused) 
Caused by: java.net.ConnectException: Connection refused (Connection refused) 

In this instanced we found the following settings changed in SsoConfig: 
Web Service Port set to 8182 in Local Override 
Web Service Scheme set to https in Local Override 

These need to be 8481 and http. The DM service runs http on port 8481 and should not be changed. 

Once that was resolved a second error appeared: 
ERROR | pool-1-thread-263 | 2018-05-30 17:34:44,705 | com.ca.im.portal.em.ds.EventProducerPoller 
| PollEventProducers javax.xml.ws.WebServiceException: Could not send Message. 
Caused by: java.net.ConnectException: ConnectException invoking https://138.193.232.13:8182/pc/center/eventProducerWS: Connection refused (Connection refused) 
Caused by: java.net.ConnectException: Connection refused (Connection refused) 

This error is caused by the following SsoConfig settings: 
WebSitePort Remote Value using 8182 
WebSitePort Local Override using 8181 

Resetting both values to use 8181 resolved that error. 

After the changes restart all four CA Performance Management services to ensure the changes are properly propagated throughout the system.
Resolution:
Ensure the port configuration post SSL HTTPS set up is correct.
Additional Information:
When only restarting the caperfcenter_sso SSO service we saw the port changes propagated to the CA Performance Center MySql netqosportal database within the performance_center_properties table.

Despite this it wasn't until all four CA Performance Center Services were restarted that the behavior was fully resolved.