Support Article
Chat server disconnected message displays in logs post upgrading
Summary
Chat server disconnected message displays in the logs after upgrading to Pega 8.2.1.
Error Messages
117[p-nio-8443-exec-2364][STANDARD][](ternal.mgmt.StreamBuilderTools) ERROR model.developer - Could not find a rule when appending a stream
com.pega.pegarules.pub.generator.RuleNotFoundException: Failed to find instance PegaCA-Work-Interaction.CPMTabChat of type Rule-HTML-Section.
Steps to Reproduce
- Launch the Interaction portal
- Log in to the Chat queues
- Set the Chat status as available
- Initiate a chat from a web portal. The chat message is not delivered to CSR
Root Cause
A defect or configuration issue in the operating environment. The chatbot must be used from Chat 8.2 onwards to initiate the chat request. The PRChat configuration is not present in the web.xml.
Resolution
Here’s the explanation for the reported behavior:
Update web.xml with the below PRChat servlet:
<servlet>
<servlet-name>PRChat</servlet-name>
<display-name>PRChat</display-name>
<description>Web Chat component, using custom authentication techniques</description>
<servlet-class>com.pega.pegarules.internal.web.servlet.WebStandardBoot</servlet-class>
<init-param>
<param-name>PegaEtierClass</param-name>
<param-value>com.pega.pegarules.session.internal.engineinterface.service.HttpAPI</param-value>
</init-param>
<init-param>
<param-name>AuthenticationType</param-name>
<param-value>PRCustom</param-value>
</init-param>
<init-param>
<param-name>RuntimeServletName</param-name>
<param-value>PRChat</param-value>
</init-param>
<init-param>
<param-name>AuthService</param-name>
<param-value>PRChatAuthentication</param-value>
</init-param>
</servlet>
Published October 24, 2019 - Updated December 2, 2021
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.