Support Article
GetResultOutClassNameFromIS failed to execute
SA-8576
Summary
User has observed that Out-of-the-box activity GetResultOutClassNameFromIS is not getting the exact BatchOutPRXXX class name and this is causing regular large number of exceptions in the logs. The system crashes once in every two weeks.
Error Messages
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
2015-03-23 00:59:47,173 [fault (self-tuning)'] [ STANDARD] [ DEMO:01.01] (rnal.PegaMKT_Work_Offer.Action) ERROR JMS|JMSActivity|Services|JMS|Requestor2 - Error could be caused due to:
Failed to open Instance/Instance is not found.
GetResultOutClassNameFromIS failed to execute
No batch output class found for customer id 0509857479 when looked up in the Interaction services
2015-03-23 00:59:47,174 [fault (self-tuning)'] [ STANDARD] [ DEMO:01.01] (Outbound.Action) ERROR JMS|JMSActivity|Services|JMS|Requestor2 - ####OFFER FAILED TO EXIST|PARSER FAILED|20150322T205947.174 GMT
2015-03-23 00:59:47,185 [fault (self-tuning)'] [ STANDARD] [ DEMO:01.01] (rnal.PegaMKT_Work_Offer.Action) ERROR JMS|JMSActivity|Services|JMS|Requestor - Error in Obj-Open
com.pega.pegarules.pub.database.NonexistentTableException: Database-NonexistentTable BatchOutPRXXX ExternalMKTData
From: (Requestor:JMSActivity)
at com.pega.pegarules.data.internal.access.TableInformationMapImpl.figureOutSchema(TableInformationMapImpl.java:837)
at com.pega.pegarules.data.internal.access.TableInformationMapImpl.lookupTableInfo(TableInformationMapImpl.java:476)
at com.pega.pegarules.data.internal.access.TableInformationMapImpl.get(TableInformationMapImpl.java:344)
at com.pega.pegarules.data.internal.dictionary.ClassMapImpl.lookupPropertyMap(ClassMapImpl.java:4364)
at com.pega.pegarules.data.internal.dictionary.ClassMapImpl.lookupSQL(ClassMapImpl.java:4260)
at com.pega.pegarules.data.internal.dictionary.ClassMapImpl.getSQL(ClassMapImpl.java:981)
at com.pega.pegarules.data.internal.access.DatabaseImpl.open(DatabaseImpl.java:3864)
at com.pegarules.generated.activity.ra_action_por_external_28e9d3bb62d3f3a1a1a07d2f95e4d523.step9_circum0(ra_action_por_external_28e9d3bb62d3f3a1a1a07d2f95e4d523.java:952)
at com.pegarules.generated.activity.ra_action_por_external_28e9d3bb62d3f3a1a1a07d2f95e4d523.perform(ra_action_por_external_28e9d3bb62d3f3a1a1a07d2f95e4d523.java:231)
at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3041)
at com.pegarules.generated.activity.ra_action_JMSact_1b1d8d063a5614b33d0c8cfe02bd129a.step7_circum0(ra_action_JMSact_1b1d8d063a5614b33d0c8cfe02bd129a.java:747)
at com.pegarules.generated.activity.ra_action_JMSact_1b1d8d063a5614b33d0c8cfe02bd129a.perform(ra_action_JMSact_1b1d8d063a5614b33d0c8cfe02bd129a.java:186)
at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3041)
at com.pega.pegarules.session.internal.mgmt.base.ThreadRunner.runActivitiesAlt(ThreadRunner.java:617)
at com.pega.pegarules.session.internal.mgmt.PRThreadImpl.runActivitiesAlt(PRThreadImpl.java:594)
at com.pega.pegarules.integration.engine.internal.services.ServiceAPI.runActivities(ServiceAPI.java:1548)
at com.pega.pegarules.session.external.engineinterface.service.EngineAPI.processRequestInner(EngineAPI.java:394)
at sun.reflect.GeneratedMethodAccessor199.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:771)
at com.pega.pegarules.session.external.engineinterface.service.EngineAPI.processRequest(EngineAPI.java:328)
at com.pega.pegarules.integration.engine.internal.services.jms.JMSListener.handleRequest(JMSListener.java:1245)
at com.pega.pegarules.integration.engine.internal.services.jms.JMSListener.runOnce(JMSListener.java:691)
at com.pega.pegarules.integration.engine.internal.services.jms.JMSListenerServant.invoke(JMSListenerServant.java:110)
at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl._invokeEngine_privact(EngineImpl.java:312)
at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl.invokeEngine(EngineImpl.java:263)
at sun.reflect.GeneratedMethodAccessor189.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethod(PRBootstrap.java:349)
at com.pega.pegarules.internal.etier.ejb.EngineBeanBoot.invokeEngine(EngineBeanBoot.java:168)
at com.pega.pegarules.internal.etier.ejb.EngineCMT_vj9np0_ELOImpl.invokeEngine(Unknown Source)
at com.pega.pegarules.session.internal.engineinterface.etier.mdb.PRJMSListener.callEngine(PRJMSListener.java:205)
at com.pega.pegarules.session.internal.engineinterface.etier.mdb.PRJMSListener.onMessage(PRJMSListener.java:127)
at sun.reflect.GeneratedMethodAccessor377.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethod(PRBootstrap.java:439)
at com.pega.pegarules.internal.etier.mdb.PRJMSListenerBoot.onMessage(PRJMSListenerBoot.java:92)
at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:388)
at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:4659)
at weblogic.jms.client.JMSSession.execute(JMSSession.java:4345)
at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:5170)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
2015-03-23 00:59:47,185 [fault (self-tuning)'] [ STANDARD] [ DEMO:01.01] (rnal.PegaMKT_Work_Offer.Action) ERROR JMS|JMSActivity|Services|JMS|Requestor - Error could be caused due to:
Failed to open Instance/Instance is not found.
GetResultOutClassNameFromIS failed to execute
No batch output class found for customer id 0504739745 when looked up in the Interaction services
Steps to Reproduce
This issue occurs in production environment and a certain use case can not be associated to it.
Root Cause
There are multiple errors in the log files of the reported environment, however following are the two major causes:
- There is a custom trigger which is not getting compiled correctly.
- The IS layer data (that is, the response data in IS_FACT_RESPONSE table) is inconsistent, because of a custom deletion script used at user's end for housekeeping of IS data. User is having LAST_OFFERED for more than one record for a CASE_ID and PROPOSITION_ID combination in IS_FACT_RESPONSE table.
In Incorrect Data scenario each FACT_RESPONSE_ID is not a parent of a LINKED_ID and the NUM_OFFERS are not sequential (yellow ones show the inconsistent mapping).
Resolution
The errors observed in the log files lead to system crash. They occur due to a faulty trigger.
It is mentioned that the data deletion script for housekeeping must be considered by the user as it should not delete data just on the basis of OFFERED_ON and CHANNEL column data.
This is prone to corrupt the IS_FACT_RESPONSE data for a CASE_ID and PROPOSITION_ID combination.
Published May 5, 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.