Question

3
Replies
1368
Views
Felicita Abad (FeliA)
AXA Group Operations PH
Pega Developer
AXA Group Operations PH
PH
FeliA Member since 2015 7 posts
AXA Group Operations PH
Posted: June 18, 2019
Last activity: July 3, 2019
Posted: 18 Jun 2019 0:08 EDT
Last activity: 3 Jul 2019 0:02 EDT
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

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!
Enterprise Application Development Dev/Designer Studio System Administration
Moderation Team has archived post, This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.