Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Issue with Index creation in PRPC 6.3 SP1

SA-8466

Summary



When trying to build the index by clicking "Build PegaRULES Index" in SMA, an error message is received:
"Failed to invoke MBean operation"
with first error code:
"ADMC0009E: The system failed to make the SOAP RPC call..."


Error Messages



Failed to invoke MBean operation
Failed to invoke an operation
java.lang.Exception: Failed to invoke MBean operation.
Name: com.pega.PegaRULES:cell=cellname,id="fcbc6413fafcf03cdd438a917a2a3369",name=com.pega.pegarules.management.internal.IndexManagement,node=nodename,process=APP1,type=enterprise opName: BuildPegaRULESIndex
Failed to invoke MBean operation
ADMC0009E: The system failed to make the SOAP RPC call: invoke


Stack Trace:

com.pega.jmx.ui.util.JMXClientException: Failed to invoke MBean operation Failed to invoke an operation java.lang.Exception: Failed to invoke MBean operation.Name: com.pega.PegaRULES:cell=cellname,id="fcbc6413fafcf03cdd438a917a2a3369",name=com.pega.pegarules.management.internal.IndexManagement,node=nodename,process=APP1,type=enterprise opName: BuildPegaRULESIndexFailed to invoke MBean operation ADMC0009E: The system failed to make the SOAP RPC call: invoke
at com.pega.jmx.ui.util.JMXClientException.wrap(JMXClientException.java:49)
at com.pega.jmx.ui.util.JMXClientUtil.invokeOpByName(JMXClientUtil.java:268)
at com.pega.jmx.ui.action.PerformIndexManagementAction.execute(PerformIndexManagementAction.java:88)
at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:484)
at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:274)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1480)
at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:506)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:575)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:668)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1230)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:779)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:478)
at com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.handleRequest(ServletWrapperImpl.java:178)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.invokeFilters(WebAppFilterManager.java:1071)
at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3774)
at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:304)
at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:981)
at com.ibm.ws.webcontainer.WSWebContainer.handleRequest(WSWebContainer.java:1662)
at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:200)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:453)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewRequest(HttpInboundLink.java:515)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.processRequest(HttpInboundLink.java:306)
at com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complete(HttpICLReadCallback.java:84)
at com.ibm.ws.ssl.channel.impl.SSLReadServiceContext$SSLReadCompletedCallback.complete(SSLReadServiceContext.java:1819)
at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:175)
at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217)
at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161)
at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:138)
at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:204)
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: java.lang.Exception: Failed to invoke MBean operation.Name: com.pega.PegaRULES:cell=cellname,id="fcbc6413fafcf03cdd438a917a2a3369",name=com.pega.pegarules.management.internal.IndexManagement,node=nodename,process=APP1,type=enterprise opName: BuildPegaRULESIndexFailed to invoke MBean operation ADMC0009E: The system failed to make the SOAP RPC call: invoke
at com.pega.jmx.connection.managenodes.Node.invoke(Node.java:103)
at com.pega.jmx.ui.util.JMXClientUtil.invokeOpByName(JMXClientUtil.java:259)
... 30 more


Steps to Reproduce



Click "Build PegaRULES Index" in SMA.

Root Cause



To begin the indexing from SMA, a SOAP request is sent from the JMXClient in SMA to the PRPC application.
The JMXClient in PRPC creates a batch requestor to perform the indexing.
Websphere application server sets a JMXConnector SOAP Request Timeout (default 180 seconds) in order to avoid the JMXConnector thread being held for an indeterminate length of time.
The indexing process has been started in the background and the pop-up window continues to show the updated status.
However, after 180 seconds, the timeout causes an exception which is returned to SMA where it is treated as a "failure to invoke MBean operation" error.


Resolution



As a later screen shows, the background indexing is completed successfully.
If an indexing operation is started from the System Settings - Search landing page, a different communication process is done and no such error is seen.

 

Published January 31, 2016 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us