CR application fails with 'Server did not respond' error

book

Article ID: 111491

calendar_today

Updated On:

Products

CA API Developer Portal CA API Gateway

Issue/Introduction



When applying CR to API Portal, it sometimes fails with the following error.
  'Server did not respond'
What is the reason for "Error: Server did not respond"?

Environment

API Portal 3.5

Resolution

The 'Server did not respond' is indicating that the applying of the patch took longer than the current maximum of 500 seconds. 
CA will increase the timeout for the next CR. 
The recommended workaround is to remove the .done file in /opt/Deployments/lrs and repeating the upgrade.