You are viewing limited content. For full access, please sign in.

Question

Question

DCC processed all jobs except a handful that got stuck on waiting

asked on January 30, 2018

Hello,

 

I have a Schedule OCR task running automatically every night for all documents that do not have OCR'd text.  When it ran last night, Job 521 to Job 556 all completed in ~1minute.  Job 557 to Job 563 were stuck on "waiting" for 8 hours until I canceled the job.  I tried creating a test workflow to schedule OCR on the same list of documents that previously were stuck on waiting and they all completed just fine.

 

Looking in the Event Viewer, I see that the DCC Developer Log contains many entries (about 1 entry / second) all containing the same Event Data:

 

SyncTasksFoundOnWorkerOperation

 

WorkerNodeId: <SERVERNAME>, workerTaskExecutionEnabled: True

 

workerTaskStatuses:

TaskId: 559.559.1; WorkerTaskStatus: OnModuleProcess

TaskId: 557.557.1; WorkerTaskStatus: OnModuleProcess

TaskId: 563.563.1; WorkerTaskStatus: OnModuleProcess

TaskId: 560.560.1; WorkerTaskStatus: OnModuleProcess

TaskId: 562.562.1; WorkerTaskStatus: OnModuleProcess

TaskId: 561.561.1; WorkerTaskStatus: OnModuleProcess

TaskId: 558.558.1; WorkerTaskStatus: OnModuleProcess

 

workerPoolTaskRecords:

TaskId: 557.557.1; TaskType: OCR.OCR; WorkerNodeId: <SERVERNAME>; WorkerPoolTaskStatus: OnWorker

TaskId: 558.558.1; TaskType: OCR.OCR; WorkerNodeId: <SERVERNAME>; WorkerPoolTaskStatus: OnWorker

TaskId: 559.559.1; TaskType: OCR.OCR; WorkerNodeId: <SERVERNAME>; WorkerPoolTaskStatus: OnWorker

TaskId: 560.560.1; TaskType: OCR.OCR; WorkerNodeId: <SERVERNAME>; WorkerPoolTaskStatus: OnWorker

TaskId: 561.561.1; TaskType: OCR.OCR; WorkerNodeId: <SERVERNAME>; WorkerPoolTaskStatus: OnWorker

TaskId: 562.562.1; TaskType: OCR.OCR; WorkerNodeId: <SERVERNAME>; WorkerPoolTaskStatus: OnWorker

TaskId: 563.563.1; TaskType: OCR.OCR; WorkerNodeId: <SERVERNAME>; WorkerPoolTaskStatus: OnWorker

 

tasksToBeRemoved:

 

tasksToBeRestartedInTheScheduler:

 

completedTasks:

 

Is there any reason that DCC would complete jobs successfully and then get stuck in a loop?  Any help would be greatly appreciated.

0 0

Answer

SELECTED ANSWER
replied on February 6, 2018

A support case was opened for the matter. The issue is due to a bug in the OCR engine regarding the despeckle process when it is configured for 1 pixel. The workaround is to use 2 or more pixels when configuring despeckle.

0 0

Replies

You are not allowed to reply in this post.
You are not allowed to follow up in this post.

Sign in to reply to this post.