Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Unable to import larger product with Jenkins



Pega application is integrated with Jenkins.

For informaiton to integrate Pega with Jenkins, refer to

A small product file is deployed successfully. However, when deploying a large product file with Jenkins, error occurs and the build fails. This error occurs about 1 minute after the deployment starts.

Error Messages

Jenkins error: [java] Error Messages : REQUEST_EXECUTION_ERROR java.lang.IllegalStateException: Response does not contain Content-Type header. The URL may be invalid

Steps to Reproduce

Migrate a product file which takes more than 1 minute to deploy.

Root Cause

A defect or configuration issue in the operating environment.
The environment used an AWS load balancer which by default had an idle connection timeout of 60 seconds. The export was not completed after 60 seconds; however, the connection was closed and control returned to the client. The expectation was for the return to use the response, from the export, in the import. Hence, it failed.

Even when the load balancer had a larger idle timeout, the process still timed out for large extracts. The export was run with requestTimeOut 300 and export.async=false. Due to the size of the export, the time was not sufficient to complete the export before the timeout was reached.


Perform the following local-change:

For synchronous export (export.async=false)
  1. Remove or increase the load balancer idle connection timeout and the request_time_out.
  2. Export smaller chunks such that the export can complete before the request_time_out that is set.

For asynchronous export (export.async=true)

  1. Switch to Async processing.
  2. Add a step in the middle to check the status using the getStatus option.
  3. Wait for the export to complete before moving to the import.

The ansychonous request generates the JobsIDs property file. Pass this file to the getStatus command instead of parsing the response to obtain the Job ID.

For more information, refer to the Pega 8.1 Help files:


Suggest Edit

Published March 27, 2019 - Updated December 2, 2021

Did you find this content helpful? Yes No

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us