Support Article
Pega lucene search is not working
SA-9423
Summary
User is unable to do context search in their PRPC environments and observes the following exception in logs.
ERROR | Rule-Connect-HTTP.Data-Find-Search.pySearchHTTPConnect|Rule-Connect-HTTP.Data-Find-Search.pySearchHTTPConnect <user> - 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: HTML
Error Messages
2015-04-21 08:50:42,823 [ WebContainer : 41] [ Developer] [AG:01.01.01] (ector.Rule_Connect_HTTP.Action) ERROR <hostname>|<DNS>|Rule-Connect-HTTP.Data-Find-Search.pySearchHTTPConnect|Rule-Connect-HTTP.Data-Find-Search.pySearchHTTPConnect <user> - 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: HTML
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: HTML
at com.pega.pegarules.integration.engine.internal.util.PRServiceUtils.mapInboundData(PRServiceUtils.java:1171)
Steps to Reproduce
In search bar, enter a searching keyword to search any contents; and observe that drop-down list does not appear.
Root Cause
Exception in the log file indicates Pega Parser is expecting clipboard page instead it received HTML content.
Setting log level status to 'DEBUG' for Pega class 'com.pega.pegarules.integration.engine.internal.ServiceHelper' logged ull content of the response.
It is an HTML document for authentication. Lucene search URL is protected and requires username and password in order to access it. Removing the access control addresses the problem.
Resolution
Lucene search URL must not be protected, hence direct access to the search node resolves the problem.
Published June 12, 2015 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.