Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Hari Mindaguditi (Hari M)
Accenture
Business Architecture Manager
Accenture
AU
Hari M Member since 2020 6 posts
Accenture
Posted: Feb 6, 2017
Last activity: Feb 14, 2017
Posted: 6 Feb 2017 0:53 EST
Last activity: 14 Feb 2017 8:19 EST
Closed
Solved

Pega 7.2.1:Connect-SOAP timeout is not working

We are on Pega 7.2.1, soap connector is not timing out per the value configured in response timeout field in Connect-SOAP rule form when connecting to a valid endpoint URL when service is not available.

Although response timeout is set on a Connect-SOAP rule, but the connection times out after longer duration than the set timeout value.

Can some one help here? Attached document for details with screenshots.

To see attachments, please log in.
Data Integration

Accepted Solution

Posted: 7 years ago
Posted: 13 Feb 2017 5:19 EST
Sudhish Othoyoth Puthiyapurayil (othos) Senior Technical Solutions Engineer
Pegasystems Inc.
IN

--Adding the update for wider audience--

Hi Hari,

As mentioned in the PDN article, this system behaves in two different way when setting the response timeout lower or higher to what the server respond.

With the Response Timeout of 30000; the service recognize that:

2017-02-07 17:35:42,139 [ http-apr-80-exec-19] [TABTHREAD1] [                    ] [hiftMgmtWeb:01.01.01] (lient.params.DefaultHttpParams) DEBUG Rule-Connect-SOAP.TNSW-Roads-SMFE-Int-SOAP-ShiftMgmtService.VerifyROLRequest mindaguh - Set parameter http.connection-manager.timeout = 30000

 

But after 21 second, the services respond with an error:

2017-02-07 17:36:03,143 [ http-apr-80-exec-19] [TABTHREAD1] [                    ] [hiftMgmtWeb:01.01.01] (.httpclient.HttpMethodDirector) INFO  Rule-Connect-SOAP.TNSW-Roads-SMFE-Int-SOAP-ShiftMgmtService.VerifyROLRequest mindaguh - I/O exception (java.net.ConnectException) caught when processing request: Connection timed out: connect

 

The default behaviour in this case, with timeout set on rule form being more that 21 seconds is to retry 3 more times; this is what actually happened:

 

Attempt 2:

Show More

--Adding the update for wider audience--

Hi Hari,

As mentioned in the PDN article, this system behaves in two different way when setting the response timeout lower or higher to what the server respond.

With the Response Timeout of 30000; the service recognize that:

2017-02-07 17:35:42,139 [ http-apr-80-exec-19] [TABTHREAD1] [                    ] [hiftMgmtWeb:01.01.01] (lient.params.DefaultHttpParams) DEBUG Rule-Connect-SOAP.TNSW-Roads-SMFE-Int-SOAP-ShiftMgmtService.VerifyROLRequest mindaguh - Set parameter http.connection-manager.timeout = 30000

 

But after 21 second, the services respond with an error:

2017-02-07 17:36:03,143 [ http-apr-80-exec-19] [TABTHREAD1] [                    ] [hiftMgmtWeb:01.01.01] (.httpclient.HttpMethodDirector) INFO  Rule-Connect-SOAP.TNSW-Roads-SMFE-Int-SOAP-ShiftMgmtService.VerifyROLRequest mindaguh - I/O exception (java.net.ConnectException) caught when processing request: Connection timed out: connect

 

The default behaviour in this case, with timeout set on rule form being more that 21 seconds is to retry 3 more times; this is what actually happened:

 

Attempt 2:

2017-02-07 17:36:03,143 [ http-apr-80-exec-19] [TABTHREAD1] [                    ] [hiftMgmtWeb:01.01.01] (.httpclient.HttpMethodDirector) INFO  Rule-Connect-SOAP.TNSW-Roads-SMFE-Int-SOAP-ShiftMgmtService.VerifyROLRequest mindaguh - Retrying request

2017-02-07 17:36:03,143 [ http-apr-80-exec-19] [TABTHREAD1] [                    ] [hiftMgmtWeb:01.01.01] (.httpclient.HttpMethodDirector) DEBUG Rule-Connect-SOAP.TNSW-Roads-SMFE-Int-SOAP-ShiftMgmtService.VerifyROLRequest mindaguh - Attempt number 2 to process request

Then ERROR AGAIN:

2017-02-07 17:36:24,148 [ http-apr-80-exec-19] [TABTHREAD1] [                    ] [hiftMgmtWeb:01.01.01] (.httpclient.HttpMethodDirector) INFO  Rule-Connect-SOAP.TNSW-Roads-SMFE-Int-SOAP-ShiftMgmtService.VerifyROLRequest mindaguh - I/O exception (java.net.ConnectException) caught when processing request: Connection timed out: connect

 

Attempt 3:

2017-02-07 17:36:24,148 [ http-apr-80-exec-19] [TABTHREAD1] [                    ] [hiftMgmtWeb:01.01.01] (.httpclient.HttpMethodDirector) DEBUG Rule-Connect-SOAP.TNSW-Roads-SMFE-Int-SOAP-ShiftMgmtService.VerifyROLRequest mindaguh - Attempt number 3 to process request

 

ERROR AGAIN:

2017-02-07 17:36:45,151 [ http-apr-80-exec-19] [TABTHREAD1] [                    ] [hiftMgmtWeb:01.01.01] (.httpclient.HttpMethodDirector) INFO  Rule-Connect-SOAP.TNSW-Roads-SMFE-Int-SOAP-ShiftMgmtService.VerifyROLRequest mindaguh - I/O exception (java.net.ConnectException) caught when processing request: Connection timed out: connect

 

Attempt 4:

2017-02-07 17:36:45,151 [ http-apr-80-exec-19] [TABTHREAD1] [                    ] [hiftMgmtWeb:01.01.01] (.httpclient.HttpMethodDirector) DEBUG Rule-Connect-SOAP.TNSW-Roads-SMFE-Int-SOAP-ShiftMgmtService.VerifyROLRequest mindaguh - Attempt number 4 to process request

 

Return failure:

2017-02-07 17:37:06,155 [ http-apr-80-exec-19] [TABTHREAD1] [                    ] [hiftMgmtWeb:01.01.01] (      internal.mgmt.Executable) ERROR Rule-Connect-SOAP.TNSW-Roads-SMFE-Int-SOAP-ShiftMgmtService.VerifyROLRequest mindaguh - Exception

com.pega.pegarules.pub.services.ResourceUnavailableException: SOAP service failed

                at com.pegarules.generated.activity.ra_action_invokeaxis2_4054e98ba19df03aff55083d242bbf9d.step15_circum0(ra_action_invokeaxis2_4054e98ba19df03aff55083d242bbf9d.java:4017)

                at com.pegarules.generated.activity.ra_action_invokeaxis2_4054e98ba19df03aff55083d242bbf9d.perform(ra_action_invokeaxis2_4054e98ba19df03aff55083d242bbf9d.java:308)

                at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3527)

                at com.pegarules.generated.activity.ra_action_invoke_8171c74e56fb26f2c41f9a69e39e4099.step8_circum0(ra_action_invoke_8171c74e56fb26f2c41f9a69e39e4099.java:1037)

                at com.pegarules.generated.activity.ra_action_invoke_8171c74e56fb26f2c41f9a69e39e4099.perform(ra_action_invoke_8171c74e56fb26f2c41f9a69e39e4099.java:189)

                at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3527)

                at com.pegarules.generated.activity.ra_action_invokeverifyrol_1378aac81270d0fe3bac40749d619d52.step4_circum0(ra_action_invokeverifyrol_1378aac81270d0fe3bac40749d619d52.java:468)

                at com.pegarules.generated.activity.ra_action_invokeverifyrol_1378aac81270d0fe3bac40749d619d52.perform(ra_action_invokeverifyrol_1378aac81270d0fe3bac40749d619d52.java:134)

                at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3527)

 

In this way the timeout is returned after more than 30000ms, which totals to about 84000ms.This concord with your observation and is completely as per system design.

 


Show Less
To see attachments, please log in.
Posted: 7 years ago
Posted: 6 Feb 2017 1:23 EST
Hari Mindaguditi (Hari M)
Accenture
Business Architecture Manager
Accenture
AU

Hi,

I have referred above article. But no use. It mentioned that "Valid URL - Connection is established and service is sending some response – In this case the connection will timeout per configured value on rule form if the service does not respond within configured time." But in my case it is not working. It is still taking more time than what i have define in Connect-SOAP rule. Please refer attached document for details.

To see attachments, please log in.

Accepted Solution

Posted: 7 years ago
Posted: 13 Feb 2017 5:19 EST
Sudhish Othoyoth Puthiyapurayil (othos) Senior Technical Solutions Engineer
Pegasystems Inc.
IN

--Adding the update for wider audience--

Hi Hari,

As mentioned in the PDN article, this system behaves in two different way when setting the response timeout lower or higher to what the server respond.

With the Response Timeout of 30000; the service recognize that:

2017-02-07 17:35:42,139 [ http-apr-80-exec-19] [TABTHREAD1] [                    ] [hiftMgmtWeb:01.01.01] (lient.params.DefaultHttpParams) DEBUG Rule-Connect-SOAP.TNSW-Roads-SMFE-Int-SOAP-ShiftMgmtService.VerifyROLRequest mindaguh - Set parameter http.connection-manager.timeout = 30000

 

But after 21 second, the services respond with an error:

2017-02-07 17:36:03,143 [ http-apr-80-exec-19] [TABTHREAD1] [                    ] [hiftMgmtWeb:01.01.01] (.httpclient.HttpMethodDirector) INFO  Rule-Connect-SOAP.TNSW-Roads-SMFE-Int-SOAP-ShiftMgmtService.VerifyROLRequest mindaguh - I/O exception (java.net.ConnectException) caught when processing request: Connection timed out: connect

 

The default behaviour in this case, with timeout set on rule form being more that 21 seconds is to retry 3 more times; this is what actually happened:

 

Attempt 2:

Show More

--Adding the update for wider audience--

Hi Hari,

As mentioned in the PDN article, this system behaves in two different way when setting the response timeout lower or higher to what the server respond.

With the Response Timeout of 30000; the service recognize that:

2017-02-07 17:35:42,139 [ http-apr-80-exec-19] [TABTHREAD1] [                    ] [hiftMgmtWeb:01.01.01] (lient.params.DefaultHttpParams) DEBUG Rule-Connect-SOAP.TNSW-Roads-SMFE-Int-SOAP-ShiftMgmtService.VerifyROLRequest mindaguh - Set parameter http.connection-manager.timeout = 30000

 

But after 21 second, the services respond with an error:

2017-02-07 17:36:03,143 [ http-apr-80-exec-19] [TABTHREAD1] [                    ] [hiftMgmtWeb:01.01.01] (.httpclient.HttpMethodDirector) INFO  Rule-Connect-SOAP.TNSW-Roads-SMFE-Int-SOAP-ShiftMgmtService.VerifyROLRequest mindaguh - I/O exception (java.net.ConnectException) caught when processing request: Connection timed out: connect

 

The default behaviour in this case, with timeout set on rule form being more that 21 seconds is to retry 3 more times; this is what actually happened:

 

Attempt 2:

2017-02-07 17:36:03,143 [ http-apr-80-exec-19] [TABTHREAD1] [                    ] [hiftMgmtWeb:01.01.01] (.httpclient.HttpMethodDirector) INFO  Rule-Connect-SOAP.TNSW-Roads-SMFE-Int-SOAP-ShiftMgmtService.VerifyROLRequest mindaguh - Retrying request

2017-02-07 17:36:03,143 [ http-apr-80-exec-19] [TABTHREAD1] [                    ] [hiftMgmtWeb:01.01.01] (.httpclient.HttpMethodDirector) DEBUG Rule-Connect-SOAP.TNSW-Roads-SMFE-Int-SOAP-ShiftMgmtService.VerifyROLRequest mindaguh - Attempt number 2 to process request

Then ERROR AGAIN:

2017-02-07 17:36:24,148 [ http-apr-80-exec-19] [TABTHREAD1] [                    ] [hiftMgmtWeb:01.01.01] (.httpclient.HttpMethodDirector) INFO  Rule-Connect-SOAP.TNSW-Roads-SMFE-Int-SOAP-ShiftMgmtService.VerifyROLRequest mindaguh - I/O exception (java.net.ConnectException) caught when processing request: Connection timed out: connect

 

Attempt 3:

2017-02-07 17:36:24,148 [ http-apr-80-exec-19] [TABTHREAD1] [                    ] [hiftMgmtWeb:01.01.01] (.httpclient.HttpMethodDirector) DEBUG Rule-Connect-SOAP.TNSW-Roads-SMFE-Int-SOAP-ShiftMgmtService.VerifyROLRequest mindaguh - Attempt number 3 to process request

 

ERROR AGAIN:

2017-02-07 17:36:45,151 [ http-apr-80-exec-19] [TABTHREAD1] [                    ] [hiftMgmtWeb:01.01.01] (.httpclient.HttpMethodDirector) INFO  Rule-Connect-SOAP.TNSW-Roads-SMFE-Int-SOAP-ShiftMgmtService.VerifyROLRequest mindaguh - I/O exception (java.net.ConnectException) caught when processing request: Connection timed out: connect

 

Attempt 4:

2017-02-07 17:36:45,151 [ http-apr-80-exec-19] [TABTHREAD1] [                    ] [hiftMgmtWeb:01.01.01] (.httpclient.HttpMethodDirector) DEBUG Rule-Connect-SOAP.TNSW-Roads-SMFE-Int-SOAP-ShiftMgmtService.VerifyROLRequest mindaguh - Attempt number 4 to process request

 

Return failure:

2017-02-07 17:37:06,155 [ http-apr-80-exec-19] [TABTHREAD1] [                    ] [hiftMgmtWeb:01.01.01] (      internal.mgmt.Executable) ERROR Rule-Connect-SOAP.TNSW-Roads-SMFE-Int-SOAP-ShiftMgmtService.VerifyROLRequest mindaguh - Exception

com.pega.pegarules.pub.services.ResourceUnavailableException: SOAP service failed

                at com.pegarules.generated.activity.ra_action_invokeaxis2_4054e98ba19df03aff55083d242bbf9d.step15_circum0(ra_action_invokeaxis2_4054e98ba19df03aff55083d242bbf9d.java:4017)

                at com.pegarules.generated.activity.ra_action_invokeaxis2_4054e98ba19df03aff55083d242bbf9d.perform(ra_action_invokeaxis2_4054e98ba19df03aff55083d242bbf9d.java:308)

                at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3527)

                at com.pegarules.generated.activity.ra_action_invoke_8171c74e56fb26f2c41f9a69e39e4099.step8_circum0(ra_action_invoke_8171c74e56fb26f2c41f9a69e39e4099.java:1037)

                at com.pegarules.generated.activity.ra_action_invoke_8171c74e56fb26f2c41f9a69e39e4099.perform(ra_action_invoke_8171c74e56fb26f2c41f9a69e39e4099.java:189)

                at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3527)

                at com.pegarules.generated.activity.ra_action_invokeverifyrol_1378aac81270d0fe3bac40749d619d52.step4_circum0(ra_action_invokeverifyrol_1378aac81270d0fe3bac40749d619d52.java:468)

                at com.pegarules.generated.activity.ra_action_invokeverifyrol_1378aac81270d0fe3bac40749d619d52.perform(ra_action_invokeverifyrol_1378aac81270d0fe3bac40749d619d52.java:134)

                at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3527)

 

In this way the timeout is returned after more than 30000ms, which totals to about 84000ms.This concord with your observation and is completely as per system design.

 


Show Less
To see attachments, please log in.

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

Pega Collaboration Center 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