SA-13649

Summary

Recurring exception shows in the logs every 30 sec or so since the installation of CPMFS FW:

Following is the user deployment set up:
PEGA 7.1.8
weblogic 12c
CPM 7.13 + CPMFS installed

After identified the Agent causing the issue. When we stop it, the exception stops showing.
To remove that exception safely and not shutting down the agent is the right thing to do.
There is no application running yet except the demo for CPM FS so it is really the basic installation with no customization.

User must know :

1) What URL this CPMProcessThreadedDocuments agent is trying to reach : an external URL or a local address ?

2) What is the best way to fix that exception?


2015-08-05 10:44:16,845 [fault (self-tuning)'] [ STANDARD] [
] [ PegaCPMFS:07.13] ( internal.mgmt.Executable) ERROR - Exception com.pega.pegarules.pub.services.ConnectorException: service URL does not contain a protocol in the correct location.
at com.pegarules.generated.activity.ra_action_pyinvokerestconnector_eb7dafe6dac00116b03b951c8add1e9a.step6_circum0(ra_action_pyinvokerestconnector_eb7dafe6dac00116b03b951c8add1e9a.java:751)
at com.pegarules.generated.activity.ra_action_pyinvokerestconnector_eb7dafe6dac00116b03b951c8add1e9a.perform(ra_action_pyinvokerestconnector_eb7dafe6dac00116b03b951c8add1e9a.java:156)
at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3500)
at com.pegarules.generated.activity.ra_action_invoke_6a91441c4f6e5048b63360383ae1b952.step7_circum0(ra_action_invoke_6a91441c4f6e5048b63360383ae1b952.java:1002)
at com.pegarules.generated.activity.ra_action_invoke_6a91441c4f6e5048b63360383ae1b952.perform(ra_action_invoke_6a91441c4f6e5048b63360383ae1b952.java:172)
at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3500)
at com.pegarules.generated.activity.ra_action_pxcallconnector_11f2ec27fb0b16bb79951eb7d74cbe15.step9_circum0(ra_action_pxcallconnector_11f2ec27fb0b16bb79951eb7d74cbe15.java:1512)
at com.pegarules.generated.activity.ra_action_pxcallconnector_11f2ec27fb0b16bb79951eb7d74cbe15.perform(ra_action_pxcallconnector_11f2ec27fb0b16bb79951eb7d74cbe15.java:226)
...

Error Messages

2015-08-05 10:44:16,845 [fault (self-tuning)'] [ STANDARD] [
] [ PegaCPMFS:07.13] ( internal.mgmt.Executable) ERROR - Exception com.pega.pegarules.pub.services.ConnectorException: service URL does not contain a protocol in the correct location.

Steps to Reproduce

Start Pega 7.1.8 server on weblogic 12c, with CPM 7.13 + CPMFS installed.
Look at weblogic standard output logs.

Root Cause

The Agent causing the issue has been identified. When we stop it, the exception stops showing.

Resolution

The PegaCPMFS instance of the Agent being referred to has been shipped as “enabled” out of the box:-

https://pdn.pega.com/documents/customer-process-manager-cpm-713-social-engagement-implementation-guide

This Agent is used for integration with social media sites, it is currently writing exceptions to the log file with each invocation (every 30 seconds) because the requisite configuration for said integration is incomplete (understandable immediately post install / at the start of a new project).

Therefore, assuming the Agent is not required at this time, one should not have any issues disabling the Agent via the checkbox to remove the exceptions from the log file.

User can then enable the Agent at a later time as/if the relate related functionality is required.