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

UnresolvedAssemblyError in NBAM application

SA-8428
 

Summary



PRRuntimeError and UnresolvedAssemblyError are reported in NBAA and NBAM application while processing the IS Fact Response.

Error Messages



2015-03-12 15:11:26,391 [fault (self-tuning)'] [ STANDARD] [ DEMO:01.01] ( services.jms.JMSListener) ERROR - Caught exception in JMS service listener DEMO_LISTENER
com.pega.pegarules.pub.PRRuntimeError: PRRuntimeError
at com.pega.pegarules.session.internal.mgmt.base.ThreadRunner.runActivitiesAlt(ThreadRunner.java:683)
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.GeneratedMethodAccessor271.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:1247)
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.GeneratedMethodAccessor203.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 sun.reflect.GeneratedMethodAccessor269.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)
Caused by: com.pega.pegarules.pub.generator.UnresolvedAssemblyError: ** {2} No code generated for expression... 32 more
2015-03-12 15:11:26,392 [fault (self-tuning)'] [ ] [ ] ( etier.mdb.PRJMSListener) ERROR - PRPC Engine invocation failed, javax.ejb.TransactionRolledbackLocalException: EJB Exception: ; nested exception is: java.lang.RuntimeException: Problem during method invocation (invokeEngine)
2015-03-12 15:11:26,410 [fault (self-tuning)'] [ STANDARD] [ DEMO:01.01] (rnal.PegaMKT_Work_Offer.Action) INFO JMS|DEMO|Services|Feedback|AE10E5B3E0B1EBE972FE2BEB2FDE4B24D - @Information: BatchClassName: Data-BatchOutPR729 | WorkID: PR-101
2015-03-12 15:11:26,424 [fault (self-tuning)'] [ STANDARD] [ DEMO:01.01] (rnal.PegaMKT_Work_Offer.Action) ERROR JMS|DEMO|Services|Feedback|AE10E5B3E0B1EBE972FE2BEB2FDE4B24D - Error in Obj-Open
com.pega.pegarules.pub.database.NonexistentTableException: Database-NonexistentTable BatchOutPR729 ExternalMKTData
From: (AE10E5B3E0B1EBE972FE2BEB2FDE4B24D:OutboundIVRUSSDFeedback)
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:383)
Caused by: com.pega.pegarules.pub.generator.UnresolvedAssemblyError: ** {2} No code generated for expression
at com.pega.pegarules.priv.FUAUtil.throwUnresolvedAssemblyError(FUAUtil.java:381)


Steps to Reproduce



Issue are reported while processing the IS Fact Responses in NBAA and NBAM application.

Root Cause



The root cause of this problem is the inconsistency in the data of IS_FACT_RESPONSE table. One CASE_ID is observed to have more than one LAST_OFFERED because of which incorrect data is being fetched in the POR activity. Another root cause of such a behaviour is that the data deletion approach followed for IS for the house keeping activities.

Resolution



You must clean-up the incorrect data in the IS_FACT_RESPONSE table, after which reported behaviour does not manifest.

Published April 22, 2015 - 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