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

prpcserviceutils failed with JSON error

SA-42195

Summary



Pega 7.2.2 is configured to use Jenkins for build deployments using prpcserviceutils as described in the PDN article.

https://pdn.pega.com/using-prpcserviceutils-and-jenkins-automated-application-deployment/using-prpcserviceutils-and

While the EXPORT succeeds, IMPORT fails with error.


Error Messages



jenkins-pega-deployment-45: Parsing response
[java] 09:56:34.694 [pool-2-thread-1] INFO [egarules.serviceclient.rest.RestResponse] - jenkins-pega-deployment-45: Parsing response of length 0
[java] 09:56:34.694 [pool-2-thread-1] INFO [egarules.serviceclient.rest.RestResponse] - jenkins-pega-deployment-45: Parsing content of type application/xml; charset=UTF-8
[java] 09:56:34.700 [main] INFO [viceclient.requestmanager.RequestManager] - Request on system jenkins-pega-deployment-45 Successful
[java] 09:56:34.716 [main] ERROR [ration.handler.custom.XMLResponseAdapter] - Error Parsing XML response
[java] org.xml.sax.SAXParseException: Premature end of file.
[java] at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:257) ~[?:1.8.0_144]
[java] at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:339) ~[?:1.8.0_144]
[java] at com.pega.pegarules.serviceclient.operation.handler.custom.PageXMLParser.parseResponseXML(PageXMLParser.java:68) ~[prdeploy.jar:?]
[java] at com.pega.pegarules.serviceclient.operation.handler.custom.XMLResponseAdapter.getResponseAsMapInner(XMLResponseAdapter.java:50) [prdeploy.jar:?]
[java] at com.pega.pegarules.serviceclient.operation.handler.custom.AbstractResponseAdapter.getResponseAsMap(AbstractResponseAdapter.java:43) [prdeploy.jar:?]
[java] at com.pega.pegarules.serviceclient.requestmanager.ServiceClientResponse.getJobStatus(ServiceClientResponse.java:64) [prdeploy.jar:?]
[java] at com.pega.pegarules.serviceclient.requestmanager.ServiceClientResponse.successList(ServiceClientResponse.java:82) [prdeploy.jar:?]
[java] at com.pega.pegarules.serviceclient.ClientMain.executeAndHandleResponse(ClientMain.java:107) [prdeploy.jar:?]
[java] at com.pega.pegarules.serviceclient.ClientMain.main(ClientMain.java:61) [prdeploy.jar:?]


Steps to Reproduce



Run the prpcserviceutils from Jenkin.


Root Cause



A defect or configuration issue in the operating environment. Jenkins "Property Content" TargetHost value had a white-space in front of the URL and prpcServiceUtils log shows "jenkins-pega-deployment-44: Parsing response of length 0", which suggests an empty response XML was returned that caused the XML parsing failure.

Resolution



Perform the following local-change: Remove the unwanted white-space from the TargetHost property in Jenkins.
Suggest Edit

Published August 26, 2017 - Updated October 8, 2020

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