Unable to view rule search results
I am able to view the search results of rules on the PEGA Developer Portal intermittently. Any reason why this might be happening and resolutions? I am using PRPC 6.3
***Updated by moderator: Lochan to close post***
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
Pegasystems
IN
Please check the search landing page (Pega Icon -> System -> Settings -> Search) to see if the search indices are up to date and all the details on that page are correct.
If there are multiple nodes in your cluster please check the logs of the current node and the search node to see if any errors or exceptions are there.
Infosys
IN
When i check the SMA for the search node. On clicking the search node i get the error
Failed to invoke an operation
java.lang.Exception: Failed to invoke MBean
operation.
Name:
com.pega.PegaRULES:cell=ZB19,id="fb733093bd8d2374e3066c1ccc018349",name=com.pega.pegarules.management.internal.SystemManagement,node=wsfpp1lpqza173,process=wsfpp1lpqza173starpuatServer,type=enterprise
opName: SystemStatus
Failed to invoke MBean operation
java.lang.NoClassDefFoundError:
com/pega/pegarules/priv/management/ManagementAPIHelper
Infosys
IN
Against the agent "SystemWorkIndexer" under system >> settings , i get the following exception :
Exception at 20150329T184401.829 GMT:
com.pega.pegarules.pub.PRRuntimeException: caught DatabaseException while trying to open conclusion Property!PXRDBERROR: Database-General Problem encountered when getting connection for database pegarules -4499 08001 [jcc][t4][2043][11550][3.64.133] Exception java.net.ConnectException: Error opening socket to server adc1db2d.ipc.us.aexp.com/ Proprietary information hidden on port 7,320 with message: Connection refused. ERRORCODE=-4499, SQLSTATE=08001CWWRA0010E: SQL State = 08001, Error Code = -4,499
Pegasystems
IN
Looks like it is unable to connect to the DB2 database on the given server host name and port. Did you try doing this outside of PRPC but from the same machine?