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

Caught unhandled exception:



User has an agent in production which will monitor the performance of service calls between Pega and Tibco application. The agent triggers an activity which in turn executes a HTTP connect request. User getting exception in the logs.

Error Messages

Exception at 20160721T060000.292 GMT: Caught unhandled exception: peer not authenticated at com.pegarules.generated.activity.ra_action_invokehttpconnector_eaefaf960376871df8c19964d12a60cb.step3_circum0( at com.pegarules.generated.activity.ra_action_invokehttpconnector_eaefaf960376871df8c19964d12a60cb.perform( at com.pega.pegarules.session.internal.mgmt.Executable.doActivity( 

Steps to Reproduce

Run the activity manually, which the agent triggers. 

Root Cause

The endpoint URL used by the user in the HTTP connect rule was secure (HTTPS), however the port used in the UTL was for non-secure (HTTP).  User was using wrong port for HTTPS endpoint.


User is suggested to update the endpoint URL with correct port to match HTTP or HTTPS. 


Published August 17, 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