Question
FBI FACE
US
Last activity: 13 May 2025 12:26 EDT
PRStackFrameNotTopException QueueProcessorExecution pyFTSIncrementalIndexer
Seeing the error below in my logs during pod startup. We have a basic kubernetes setup and just one Pega node. I'm not sure what to do. Any help would be greatly appreciated.
Seeing the error below in my logs during pod startup. We have a basic kubernetes setup and just one Pega node. I'm not sure what to do. Any help would be greatly appreciated.
2025-01-15 08:15:58,501 [, Partitions=[0,1,2]] [ STANDARD] [ ] [ ] ( QueueProcessorExecution) ERROR B9EARSK6F4FF0833YM4OH0FVM4454BWNOA System - [QueueProcessor:pyFTSIncrementalIndexer] [MessageID : 3abcf19e-e5b6-4c91-b2d4-08190e783b83] Exception while processing [QueueProcessor:pyFTSIncrementalIndexer] [MessageID : 3abcf19e-e5b6-4c91-b2d4-08190e783b83] , com.pega.pegarules.pub.context.PRStackFrameNotTopException: Specified stack frame 'RULE-OBJ-ACTIVITY SYSTEM-QUEUE-FTSINCREMENTALINDEXER PZFTSINCREMENTALINDEXERUSINGQP #20180713T132850.953 GMT Step: 2 Circum: 0' does not match top of stack: 'Java' at com.pega.pegarules.session.internal.mgmt.Executable.popStackFrame(Executable.java:2166) ~[prprivate-session.jar:?] at com.pegarules.generated.activity.ra_action_pzftsincrementalindexerusingqp_9bea4731ceaaebca3afdc57e01184f37.perform(ra_action_pzftsincrementalindexerusingqp_9bea4731ceaaebca3afdc57e01184f37.java:95) ~[?:?] at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:2888) ~[prprivate-session.jar:?] at com.pega.dsm.dnode.impl.dataflow.asyncexecutor.execution.QPExecution.runActivity(QPExecution.java:112) ~[d-node.jar:?] at com.pega.dsm.dnode.impl.dataflow.asyncexecutor.execution.QPExecution.run(QPExecution.java:67) ~[d-node.jar:?] at com.pega.dsm.dnode.impl.dataflow.asyncexecutor.QueueProcessorExecutor.execute(QueueProcessorExecutor.java:116) ~[d-node.jar:?] at com.pega.dsm.dnode.impl.dataflow.asyncexecutor.QueueProcessorOnlyOnceExecutionStrategy.run(QueueProcessorOnlyOnceExecutionStrategy.java:167) ~[d-node.jar:?] at com.pega.dsm.dnode.impl.dataflow.asyncexecutor.QueueProcessorUsageReportingExecutionStrategy.run(QueueProcessorUsageReportingExecutionStrategy.java:83) ~[d-node.jar:?] at com.pega.dsm.dnode.impl.dataflow.asyncexecutor.QueueProcessorUsageReportingExecutionStrategy.lambda$execute$0(QueueProcessorUsageReportingExecutionStrategy.java:64) ~[d-node.jar:?] at com.pega.pegarules.session.internal.PRSessionProviderImpl.performTargetActionWithLock(PRSessionProviderImpl.java:1379) ~[prprivate-session.jar:?] at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:1122) ~[prprivate-session.jar:?] at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:1003) ~[prprivate-session.jar:?] at com.pega.pegarules.session.internal.PRSessionProviderImplForModules.doWithRequestorLocked(PRSessionProviderImplForModules.java:83) ~[prprivate-session.jar:?] at com.pega.dsm.dnode.impl.dataflow.asyncexecutor.QueueProcessorUsageReportingExecutionStrategy.execute(QueueProcessorUsageReportingExecutionStrategy.java:52) ~[d-node.jar:?] at com.pega.platform.executor.internal.LogContextDecorator.runInDecoratedScope(LogContextDecorator.java:38) ~[pega-executor.jar:?] at com.pega.dsm.dnode.impl.dataflow.asyncexecutor.QueueProcessorDataFlowFactory$1$1.onNext(QueueProcessorDataFlowFactory.java:98) ~[d-node.jar:?] at com.pega.dsm.dnode.impl.dataflow.asyncexecutor.QueueProcessorDataFlowFactory$1$1.onNext(QueueProcessorDataFlowFactory.java:79) ~[d-node.jar:?] at com.pega.dsm.dnode.api.dataflow.DataFlowStage$StageInputSubscriber.onNext(DataFlowStage.java:555) ~[d-node.jar:?] at com.pega.dsm.dnode.api.dataflow.DataFlowStage$StageInputSubscriber.onNext(DataFlowStage.java:480) ~[d-node.jar:?] at com.pega.dsm.dnode.api.dataflow.DataFlowExecutor$QueueBasedDataFlowExecutor$2.process(DataFlowExecutor.java:329) ~[d-node.jar:?] at com.pega.dsm.dnode.api.dataflow.DataFlowExecutor$QueueBasedDataFlowExecutor.runEventLoop(DataFlowExecutor.java:218) ~[d-node.jar:?] at com.pega.dsm.dnode.api.dataflow.DataFlow$2.emit(DataFlow.java:347) ~[d-node.jar:?] at com.pega.dsm.dnode.impl.stream.DataObservableImpl.subscribe(DataObservableImpl.java:59) ~[d-node.jar:?] at com.pega.dsm.dnode.impl.dataflow.task.strategy.ExecutionStrategy.executeDataFlow(ExecutionStrategy.java:122) ~[d-node.jar:?] at com.pega.dsm.dnode.impl.dataflow.task.strategy.MultiplePartitionExecution.executePartitions(MultiplePartitionExecution.java:87) ~[d-node.jar:?] at com.pega.dsm.dnode.impl.dataflow.service.run.ExecutePartitionsRunnable.executeDataFlowWithPartitions(ExecutePartitionsRunnable.java:86) ~[d-node.jar:?] at com.pega.dsm.dnode.impl.dataflow.service.run.ExecutePartitionsRunnable.access$900(ExecutePartitionsRunnable.java:34) ~[d-node.jar:?] at com.pega.dsm.dnode.impl.dataflow.service.run.ExecutePartitionsRunnable$1.run(ExecutePartitionsRunnable.java:67) ~[d-node.jar:?] at com.pega.dsm.dnode.impl.dataflow.service.run.ExecutePartitionsRunnable$1.run(ExecutePartitionsRunnable.java:62) ~[d-node.jar:?] at com.pega.dsm.dnode.util.PrpcRunnable.execute(PrpcRunnable.java:77) ~[d-node.jar:?] at com.pega.dsm.dnode.impl.prpc.service.ServiceHelper.executeInPrpcContextInternal(ServiceHelper.java:305) ~[d-node.jar:?] at com.pega.dsm.dnode.impl.prpc.service.ServiceHelper.executeInPrpcContext(ServiceHelper.java:150) ~[d-node.jar:?] at com.pega.dsm.dnode.impl.dataflow.service.run.ExecutePartitionsRunnable.call(ExecutePartitionsRunnable.java:62) ~[d-node.jar:?] at com.pega.dsm.dnode.impl.dataflow.service.run.ExecutePartitionsRunnable.call(ExecutePartitionsRunnable.java:34) ~[d-node.jar:?] at com.google.common.util.concurrent.TrustedListenableFutureTask$TrustedFutureInterruptibleTask.runInterruptibly(TrustedListenableFutureTask.java:131) ~[guava-32.1.3-jre.jar:?] at com.google.common.util.concurrent.InterruptibleTask.run(InterruptibleTask.java:76) ~[guava-32.1.3-jre.jar:?] at com.google.common.util.concurrent.TrustedListenableFutureTask.run(TrustedListenableFutureTask.java:82) ~[guava-32.1.3-jre.jar:?] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) ~[?:1.8.0_322] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) ~[?:1.8.0_322] at com.pega.dsm.dnode.util.PrpcRunnable$1.run(PrpcRunnable.java:69) ~[d-node.jar:?] at com.pega.dsm.dnode.util.PrpcRunnable$1.run(PrpcRunnable.java:66) ~[d-node.jar:?] at com.pega.dsm.dnode.util.PrpcRunnable.execute(PrpcRunnable.java:77) ~[d-node.jar:?] at com.pega.dsm.dnode.impl.prpc.PrpcThreadFactory$PrpcThread.run(PrpcThreadFactory.java:164) ~[d-node.jar:?]
***Edited by Moderator Marije to add Capability tags***
Accepted Solution
Updated: 13 May 2025 12:26 EDT
Pegasystems Inc.
GB
@JohnF17280011 Below a GenAI document-based response:
The PRStackFrameNotTopException during the startup of the pyFTSIncrementalIndexer may indicate issues with the queue processor's execution context. This can occur if the queue processor is not able to initialize properly due to underlying conditions in your environment. It is essential to check the status of your indexes and ensure that the Stream Service is running correctly. If the status of your indexes is RED or YELLOW, the pyFTSIncrementalIndexer may automatically turn off. Additionally, you may want to review the logs for any errors related to the initialization of Elasticsearch or the state of the Kafka partitions, as these can also affect the queue processor's ability to start successfully.
Please check the Reference below:
pyFTSIncrementalIndexer not running or turning off automatically
As this may need in-depth checkx, please log a support incident via the MSP if you do not get the help you need on this forum.