Support Article

NumberFormatException entries in logs after upgrade to Pega 7.2



User has upgraded from Pega 7.1.8 to Pega 7.2.

After the upgrade user is noticing the following exception message in PegaRULES logfile: Caught unhandled exception: java.lang.NumberFormatException: For input string: "Port"

Error Messages

Caused by: java.lang.NumberFormatException: For input string: "Port"
at java.lang.NumberFormatException.forInputString(
at java.lang.Integer.parseInt(
at java.lang.Integer.parseInt(
at com.pega.apache.http.client.utils.URIUtils.extractHost(
at com.pega.apache.http.impl.client.AbstractHttpClient.determineTarget(
at com.pega.apache.http.impl.client.AbstractHttpClient.execute(
at com.pegarules.generated.activity.ra_action_pyinvokerestconnector_3f88330e50b57463fbf3f06db192aa5e.step12_circum0(

Steps to Reproduce

  1. Upgrade from Pega 7.1.8 to Pega 7.2.
  2. Restart the application server and invoke a REST connector.

Root Cause

An issue in the custom application code or rules.

The pyInvokeRESTConnector activity rule was customized and overwritten in Pega 7.1.8.

The Pega Out-of-the-box (OOTB) version of this activity has changed between Pega 7.1.8 and Pega 7.2.

​The additional changes present in OOTB version of pyInvokeRESTConnector in Pega 7.2 were missing from the custom version of pyInvokeRESTConnector overwritten in Pega 7.1.8.


The following is the local change provided for the issue:

Customize the Pega 7.2 OOTB version of pyInvokeRESTConnector activity instead of using the custom Pega 7.1.8 version of this activity after upgrade to Pega 7.2.

Published August 29, 2016 - Updated September 6, 2016

Have a question? Get answers now.

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