Support Article

Declare page not getting loaded properly after server restart

SA-25865

Summary



Declare pages are not getting loaded after each server restart. Our JMS MDB listener's use  global resource settings defined in a Declare page.
  1. Our application has file listeners and JMSMDB listeners. Both of them use a global resource settings declare page to define file location, queue name etc.
  2. When the server restarts, the file listener does not come up automatically. To analyse this, the JMSMDB listeners have been disabled.
  3. When the server restarts, the file listener is trying to load the declare page, but the load is not successful. As the declare page is not loaded, the file source location is not present and hence the file listener failed to initialise.
  4. How can the data page be loaded before the file listener comes up?
  5. Surprisingly this issue is not coming in all environments.
     

Error Messages



2016-06-27 14:00:27,859 [.PRPCWorkManager : 0] [ STANDARD] [an_app:01.27] (ernal.async.BatchRequestorTask) ERROR an_operator - Batch activity "Rule-Connect-JMS.ChildInvoke" threw:
com.pega.pegarules.pub.PRRuntimeError: PRRuntimeError
at com.pega.pegarules.session.internal.mgmt.base.ThreadRunner.runActivitiesAlt(ThreadRunner.java:712)
at com.pega.pegarules.session.internal.mgmt.base.ThreadRunner.runActivities(ThreadRunner.java:572)
at com.pega.pegarules.session.internal.mgmt.PRThreadImpl.runActivities(PRThreadImpl.java:453)
at com.pega.pegarules.session.internal.async.agent.QueueProcessor.executeBatchTask(QueueProcessor.java:257)
at com.pega.pegarules.session.internal.async.agent.QueueProcessor.execute(QueueProcessor.java:320)
at com.pega.pegarules.session.internal.async.BatchRequestorTask.run(BatchRequestorTask.java:945)
at com.pega.pegarules.session.internal.PRSessionProviderImpl.performTargetActionWithLock(PRSessionProviderImpl.java:1259)
at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:1008)
at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:901)
at com.pega.pegarules.session.internal.async.BatchRequestorTask.run(BatchRequestorTask.java:670)
at com.pega.pegarules.session.internal.async.Agent.runBatchTask(Agent.java:815)
at com.pega.pegarules.session.internal.engineinterface.etier.impl.AsyncServant.processAsyncTask(AsyncServant.java:230)
at com.pega.pegarules.session.internal.engineinterface.etier.impl.AsyncServant.invoke(AsyncServant.java:167)
at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl._invokeEngine_privact(EngineImpl.java:315)
at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl.invokeEngine(EngineImpl.java:263)
at com.pega.pegarules.session.internal.engineinterface.etier.ejb.EngineBean.invokeEngine(EngineBean.java:225)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:611)
at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethod(PRBootstrap.java:367)
at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethodPropagatingThrowable(PRBootstrap.java:408)
at com.pega.pegarules.boot.internal.extbridge.AppServerBridgeToPega.invokeMethodPropagatingThrowable(AppServerBridgeToPega.java:223)
at com.pega.pegarules.boot.internal.extbridge.AppServerBridgeToPega.invokeMethodPropagatingException(AppServerBridgeToPega.java:245)
at com.pega.pegarules.internal.etier.ejb.EngineBeanBoot.invokeEngine(EngineBeanBoot.java:168)
at com.pega.pegarules.internal.etier.interfaces.EJSLocalStatelessEngineBMT_f2439d86.invokeEngine(Unknown Source)
at com.pega.pegarules.session.internal.engineinterface.etier.mdb.PRAsync.processRequest(PRAsync.java:155)
at com.pega.pegarules.session.internal.engineinterface.etier.asynchbeans.AsyncTask.run(AsyncTask.java:64)
at com.pega.pegarules.session.internal.engineinterface.etier.asynchbeans.RunnableWrapper.run(RunnableWrapper.java:71)
at com.ibm.ws.asynchbeans.J2EEContext$RunProxy.run(J2EEContext.java:271)
at java.security.AccessController.doPrivileged(AccessController.java:399)
at com.ibm.ws.asynchbeans.J2EEContext.run(J2EEContext.java:797)
at com.ibm.ws.asynchbeans.WorkWithExecutionContextImpl.go(WorkWithExecutionContextImpl.java:222)
at com.ibm.ws.asynchbeans.ABWorkItemImpl.run(ABWorkItemImpl.java:206)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1731)
Caused by:
com.pega.pegarules.pub.context.PRAbandonProcessingException: PRRuntimeError
at com.pega.pegarules.session.internal.mgmt.Executable.activityStepProlog(Executable.java:1197)
at com.pegarules.generated.activity.ra_action_invokejmsconnector_1312bbe05af1824b176aa2dd86b5d68e.step1_circum0(ra_action_invokejmsconnector_1312bbe05af1824b176aa2dd86b5d68e.java:224)
at com.pegarules.generated.activity.ra_action_invokejmsconnector_1312bbe05af1824b176aa2dd86b5d68e.perform(ra_action_invokejmsconnector_1312bbe05af1824b176aa2dd86b5d68e.java:69)
at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3500)
at com.pega.pegarules.session.internal.mgmt.Executable.invokeActivity(Executable.java:10521)
at com.pegarules.generated.activity.ra_action_invoke_a89c88dc2333f1fdb308dd3a64dd4f5a.step4_circum0(ra_action_invoke_a89c88dc2333f1fdb308dd3a64dd4f5a.java:366)
at com.pegarules.generated.activity.ra_action_invoke_a89c88dc2333f1fdb308dd3a64dd4f5a.perform(ra_action_invoke_a89c88dc2333f1fdb308dd3a64dd4f5a.java:120)
at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3500)
at com.pegarules.generated.activity.ra_action_childinvoke_34be484f442477bb0a926c4384d3a9e8.step4_circum0(ra_action_childinvoke_34be484f442477bb0a926c4384d3a9e8.java:393)
at com.pegarules.generated.activity.ra_action_childinvoke_34be484f442477bb0a926c4384d3a9e8.perform(ra_action_childinvoke_34be484f442477bb0a926c4384d3a9e8.java:126)
at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3500)
at com.pega.pegarules.session.internal.mgmt.base.ThreadRunner.runActivitiesAlt(ThreadRunner.java:646)
... 34 more


Steps to Reproduce

  1. Restart the server.
  2. The log file contains the reported stack trace.
  3. The Data page not getting loaded with the expected data.


Root Cause



A software use or operation error 

Resolution



The connect-JMS method has been configured with RUN IN PARALLEL option, as such the connect-wait method should be used after the connect-JMS call.

Published July 21, 2016 - Updated July 30, 2016

Have a question? Get answers now.

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