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

dotNet Connector Doesn't Obey Timeout Values above 120s



PRPC Rule-Connet-dotNet is calling dotNet service that has the potential to run for a very long time (15-20mins and this is completely acceptable). However, setting in dotNet Connector's "Service" tab seems to behave Response Timeout above 300s but times out  before 300secs. 

Error Messages

2014-09-15 13:21:37,695 [ WebContainer : 5] [ STANDARD] [] (ngineinterface.service.HttpAPI) ERROR PRRuntimeError
at com.pega.pegarules.session.internal.mgmt.base.ThreadRunner.runActivitiesAlt(
Caused by: SOAP service failed
at com.pegarules.generated.activity.ra_action_invokeaxis2_6a5435ee882cb1f48171c451972ab9c2.step16_circum0(
Caused by: Connection reset

Steps to Reproduce

- Create a dotNet Connector
- Set the Connector Timeout to 300s
- Connect to a service that takes more than 300s.
- Observe connector times out well before 300s.

Root Cause

When tried using SOAP UI outside of PRPC - It fails with the same exception 'Connection reset'.


Connection to the dotNet service is reset at different level & the issue can be reproduced outside of Pega Connector. Verify the connection timeout at the webserver or proxy level.

Published January 31, 2016 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

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