So, when something goes wrong during document processing, the usual thing
that happens is that the document is pushed back onto the document queue
but with a processing time some distance in the future. How far in the
future depends on the details of exception handling within the connector.
But a
Yes sorry I wrongly described the 1/: the runtime exception happens in the
processDocument on the first and only document found in the seeding phase.
Here is the stack trace:
WARN 2022-03-22T13:07:03,761 (Worker thread '13') -
MCF|MCF-agent|apache.manifoldcf.connectors|JCIFS: Possibly
Specifically, the stuffer thread is responsible for finding documents to
process and getting them to the worker threads via the internal queue that
the worker threads wait on. The stuffer thread uses a query to do this.
Either the query is not finding any documents, or the stuffer thread is
down.
' 1/ On the first and only one document of the seeding phase encountered, a
runtime exception is triggered'
The worker threads do not handle seeding. If a runtime exception takes
place during seeding, no documents will be queued, and that is the
problem. The state of the job must be incorrectly
Hi Karl,
I had some time to investigate the problem I exposed in my first mail, and here
is the behavior I observed:
1/ On the first and only one document of the seeding phase encountered, a
runtime exception is triggered
2/ The runtime exception is catched by the WorkerThread, logged, and the
