Fatal transport error: Unexpected response status: 502

Document ID : KB000095167
Last Modified Date : 18/05/2018
Show Technical Document Details
User may encounter the following error while applying a Cumulative Release (CR) onto their Portal 3.5

# sh upgrade-v3.5.CR7.sh 

Applying v3.5.CR7 update... done

Starting catalina
Waiting for catalina to start, please be patient...

Using host: https://portal.sample.local
Enter your admin username: admin
Enter your admin password:
Waiting for XSL
Applying patch v3.5.CR7.cmspatch
Skipping patch v3.5.CR1-phrases.cmspatch already applied
Skipping patch v3.5.CR2-phrases.cmspatch already applied
Skipping patch v3.5.CR3-phrases.cmspatch already applied
Skipping patch v3.5.CR3-content.cmspatch already applied
Skipping patch v3.5.CR4-phrases.cmspatch already applied
Skipping patch v3.5.CR6-phrases.cmspatch already applied
Applying patch v3.5.CR7-content.cmspatch
Skipping patch v3.5.CR7-content.cmspatch already applied
Skipping patch v3.5.CR7-content.cmspatch already applied
Skipping patch v3.5.CR7-content.cmspatch already applied
Applying patch v3.5.CR7-phrases.cmspatch
Waiting for queues....
Regnerating template editors
Regenerating standard files
Fatal transport error: Unexpected response status: 502
org.apache.http.client.ClientProtocolException: Unexpected response status: 502
at com.ca.portal.client.CMSClient$1.handleResponse(CMSClient.java:45)
at com.ca.portal.client.CMSClient$1.handleResponse(CMSClient.java:1)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:218)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:160)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:136)
at com.ca.portal.client.CMSClient.main(CMSClient.java:153

This usually may happen when the patch process is taking longer than what the HTTP daemon is willing to wait.

CA API Portal 3.5
In order to fix above error, the following steps should help:
  • Remove related v3.5.CR(x).done file under /opt/Deployment/lrs folder if exists. This will allow Portal to re-run the patch via upgrade script.
  • Edit /etc/httpd/conf/httpd.conf and change default Timeout value from 60 to 300
  • Enable new settings by running in the command prompt: service httpd reload
  • Reinstall the patch.