Support Article

Invalid clipboard stream detected exception in log file

SA-7235

Summary



You are frequently observing below "Invalid clipboard stream detected" exception in log file without observing any impact on user experience.


Error Messages



2015-02-18 02:41:44,799 [ WebContainer : 12] [ STANDARD] [ ] [ Demo:04.01.10] ( engine.internal.ServiceHelper) ERROR xxx.xxx.com|1.1.1.1|Rule-Connect-HTTP.Data-Find-Search.pySearchHTTPConnect user01 - Caught unexpected exception mapping inbound data: Invalid clipboard stream detected in module com.pega.pegarules.data.internal.clipboard.XMLStream.newStream(String, StorageStream). Reason: sax parse error: Expecting root element as PRPC "pagedata", instead found: H1
2015-02-18 02:41:44,806 [ WebContainer : 12] [ STANDARD] [ ] [ Demo:04.01.10] ( internal.mgmt.Executable) ERROR xxx.xxx.com|1.1.1.1 user01 - Exception
com.pega.pegarules.pub.services.InboundMappingException: Caught unexpected exception mapping inbound data: Invalid clipboard stream detected in module com.pega.pegarules.data.internal.clipboard.XMLStream.newStream(String, StorageStream). Reason: sax parse error: Expecting root element as PRPC "pagedata", instead found: H1
at com.pega.pegarules.integration.engine.internal.util.PRServiceUtils.mapInboundData(PRServiceUtils.java:1260)
at com.pegarules.generated.activity.ra_action_invokehttpconnector_b388afe9c76edf2991b3a563a1924848.step3_circum0(ra_action_invokehttpconnector_b388afe9c76edf2991b3a563a1924848.java:1443)
at com.pegarules.generated.activity.ra_action_invokehttpconnector_b388afe9c76edf2991b3a563a1924848.perform(ra_action_invokehttpconnector_b388afe9c76edf2991b3a563a1924848.java:103)
at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3375)
at com.pegarules.generated.activity.ra_action_invoke_2fe5642b820e33c92609b4452e4b1411.step7_circum0(ra_action_invoke_2fe5642b820e33c92609b4452e4b1411.java:950)
at com.pegarules.generated.activity.ra_action_invoke_2fe5642b820e33c92609b4452e4b1411.perform(ra_action_invoke_2fe5642b820e33c92609b4452e4b1411.java:172)
at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3375)
at com.pegarules.generated.activity.ra_action_pzsearch_f5e449d2579c7de3984dc65cf2a19006.step4_circum0(ra_action_pzsearch_f5e449d2579c7de3984dc65cf2a19006.java:505)
at com.pegarules.generated.activity.ra_action_pzsearch_f5e449d2579c7de3984dc65cf2a19006.perform(ra_action_pzsearch_f5e449d2579c7de3984dc65cf2a19006.java:121)
..more..


Steps to Reproduce



Setup the search in load balanced multi-node environment.

Root Cause



Going by log snippet, it seems to be an issue with Search configurations. Exception suggests that you are not getting valid response from index node; you are getting some error code and thus HTML instead. This could be request not reaching the indexing node and was intercepted by some proxy in between. You have a load balancer that routes the request to one of the 2 nodes. You need to setup the search properly; as it is ML7, it will be ElasticSearch instead of Lucene.

Moreover, in Pega 7, HTTP Connector does not skip parsing the response body in case of bad responses anymore unlike PRPC 6.x version and thus you do not see these kind of exception in log file of older version.

Resolution



After building the ElasticSearch up and working, you aren't seeing reported exception anymore.
Suggest Edit

Published January 31, 2016 - Updated October 8, 2020

Did you find this content helpful?

Have a question? Get answers now.

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