SA-11784

Summary

com.pega.apache.axis2.AxisFault Exception in Lucene Search.

Error Messages

2015-06-04 13:58:44,939 [   WebContainer : 11] [ Developer] [   your_app:01.03.01] (esults.Embed_ListParams.Action) ERROR your_sever your_user - There was an error in loading Declare_AgentStatus page
com.pega.pegarules.pub.PRRuntimeException: Error loading Declare_AgentStatus with definition RULE-DECLARE-PAGES DECLARE_AGENTSTATUS #20120713T020321.907 GMT using activity {pyActivityName=pzCheckAgentStatus, pxObjClass=Rule-Obj-Activity, pyClassName=Pega-Search-AgentStatus}
    at com.pega.pegarules.exec.internal.declare.infengine.pages.DeclarativePageDirectoryImpl.runLoadActivity(DeclarativePageDirectoryImpl.java:944)
    at com.pega.pegarules.exec.internal.declare.infengine.pages.DeclarativePageDirectoryImpl.findDeclarativePage(DeclarativePageDirectoryImpl.java:518)
    at com.pega.pegarules.session.internal.mgmt.PRNodeImpl.findDeclarativePage(PRNodeImpl.java:2037)
    at com.pega.pegarules.session.internal.mgmt.base.ThreadPageDir.findDeclarativePage(ThreadPageDir.java:997)
.
.
.
    at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:775)
    at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:905)
    at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1702)
Caused by: 
com.pega.pegarules.pub.services.RemoteApplicationException: SOAP service failed
    at com.pegarules.generated.activity.ra_action_invokeaxis2_efdcaff8235c882865ae58f4a00da6fd.step15_circum0(ra_action_invokeaxis2_efdcaff8235c882865ae58f4a00da6fd.java:3821)
    at com.pegarules.generated.activity.ra_action_invokeaxis2_efdcaff8235c882865ae58f4a00da6fd.perform(ra_action_invokeaxis2_efdcaff8235c882865ae58f4a00da6fd.java:311)
.
.
.
Caused by: 
com.pega.apache.axis2.AxisFault: Transport error: 404 Error: Not Found
    at com.pega.apache.axis2.transport.http.HTTPSender.handleResponse(HTTPSender.java:312)
    at com.pega.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:200)
.
.
.

Steps to Reproduce

There is no specific use case to reproduce this behavior.

Root Cause

Incorrect Host ID is mapped in HostID field of search landing page, which can be found in PegaButton > System > Settings > Search.
 

Resolution

Reported behavior was resolved with the following steps:

1. Identify the correct node ID where indexing has been performed. 
2. Map the same node ID in the HostID field of search landing page located at PegaButton > System > Settings > Search.