Question
Closed
Solved
pyFTSIncrementatlIndexer cannot be started as it is in '-' state error
Hi All,
Please help to resolve the error encountered in Pega Queue processor rule.
Pega Framework version: Pega 8.1.3
Show More
Hi All,
Please help to resolve the error encountered in Pega Queue processor rule.
Pega Framework version: Pega 8.1.3
2019-06-17 00:39:25,005 [CHEDULER_THREAD_POOL] [ STANDARD] [ ] [ ] (ndexer.DistributedIndexerAgent) ERROR - Exception while performing queue processor management operation
com.pega.pegarules.pub.context.QueueProcessorManagementOperationsException: Queue processor: pyFTSIncrementalIndexer cannot be started as it is in '-' state
at com.pega.platform.executor.queueprocessor.internal.QueueProcessorManagementOperationsImpl.startQueueProcessor(QueueProcessorManagementOperationsImpl.java:682) ~[pega-executor.jar:?]
at com.pega.pegarules.management.internal.system.operations.QueueProcessorManagementAPI.startQueueProcessor(QueueProcessorManagementAPI.java:73) ~[prprivate.jar:?]
at com.pega.platform.pegasearch.indexer.internal.DistributedIndexerAgent.manageIncrementalIndexer(DistributedIndexerAgent.java:168) ~[pegasearch.jar:?]
at com.pega.pegarules.session.internal.mgmt.Executable.manageIncrementalIndexer(Executable.java:11380) ~[prprivate.jar:?]
at com.pegarules.generated.activity.ra_action_pzmanageincrementalindexer_921cf20315b934ab9b56a5fa027e14bf.step1_circum0(ra_action_pzmanageincrementalindexer_921cf20315b934ab9b56a5fa027e14bf.java:161) ~[?:?]
at com.pegarules.generated.activity.ra_action_pzmanageincrementalindexer_921cf20315b934ab9b56a5fa027e14bf.perform(ra_action_pzmanageincrementalindexer_921cf20315b934ab9b56a5fa027e14bf.java:70) ~[?:?]
at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3556) ~[prprivate.jar:?]
at com.pega.platform.executor.jobscheduler.internal.ActivityExecutor.runActivity(ActivityExecutor.java:33) ~[pega-executor.jar:?]
at com.pega.platform.executor.jobscheduler.internal.ActivityExecutor.executeActivity(ActivityExecutor.java:25) ~[pega-executor.jar:?]
at com.pega.platform.executor.jobscheduler.internal.ActivityProcessor.execute(ActivityProcessor.java:55) ~[pega-executor.jar:?]
at com.pega.platform.executor.jobscheduler.internal.ActivityProcessor.run(ActivityProcessor.java:108) ~[pega-executor.jar:?]
at com.pega.pegarules.session.internal.PRSessionProviderImpl.performTargetActionWithLock(PRSessionProviderImpl.java:1366) ~[prprivate.jar:?]
at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:1109) ~[prprivate.jar:?]
at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:990) ~[prprivate.jar:?]
at com.pega.pegarules.session.internal.PRSessionProviderImplForModules.doWithRequestorLocked(PRSessionProviderImplForModules.java:55) ~[prprivate.jar:?]
at com.pega.platform.executor.jobscheduler.internal.JobSchedulerProcessor.execute(JobSchedulerProcessor.java:48) ~[pega-executor.jar:?]
at com.pega.platform.executor.jobscheduler.scheduler.internal.JobRunTimeImpl.execute(JobRunTimeImpl.java:67) ~[executor.jar:?]
at com.pega.platform.executor.jobscheduler.scheduler.internal.JobRunTimeDecorator.execute(JobRunTimeDecorator.java:57) ~[executor.jar:?]
at com.pega.platform.executor.jobscheduler.scheduler.internal.JobRunTimeDecorator.execute(JobRunTimeDecorator.java:57) ~[executor.jar:?]
at com.pega.platform.executor.jobscheduler.scheduler.internal.JobExecutionTemplate.executeJob(JobExecutionTemplate.java:45) ~[executor.jar:?]
at com.pega.platform.executor.jobscheduler.scheduler.internal.JobExecutionTemplate.run(JobExecutionTemplate.java:35) ~[executor.jar:?]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) ~[?:1.8.0_152]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) ~[?:1.8.0_152]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) ~[?:1.8.0_152]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) ~[?:1.8.0_152]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_152]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_152]
at java.lang.Thread.run(Thread.java:748) [?:1.8.0_152]
Appreciate if you could response ASAP as this is one of the causes why our DEV server becoming slow as this has been happened consecutively. Thank you!
Show Less
Accepted Solution
Posted: 5 years ago
Updated: 7 months ago
Updated: 26 Apr 2024 10:47 EDT
Pegasystems Inc.
Pegasystems Inc.
IN
Hi ,
Pega 8.x requires at least one stream node (or a universal node).
Could you please check if you added stream node in Decisioning-->Infrastracture-->Services-->Stream path and if the node is up and running?
Regards,
Waseem Khan
Posted: 5 years ago
Pegasystems Inc.
IN
Hi,
What is the status of corresponding data flow. You can find data flow status by opening data flow work object from queue processor landing page.
Also, check if stream service is up and running.
Accepted Solution
Posted: 5 years ago
Updated: 7 months ago
Updated: 26 Apr 2024 10:47 EDT
Pegasystems Inc.
Pegasystems Inc.
IN
Hi ,
Pega 8.x requires at least one stream node (or a universal node).
Could you please check if you added stream node in Decisioning-->Infrastracture-->Services-->Stream path and if the node is up and running?
Regards,
Waseem Khan
Posted: 5 years ago
Updated: 7 months ago
Updated: 26 Apr 2024 10:47 EDT
ING Business Shared Services Inc.
ING Business Shared Services Inc.
PH
hi khanw2,
It is down, and tried to up, and it is working as expected now, thank you!