Hi, can you try Ducc 2.0.0? It was recently released into Apache. One of the key changes was to remove queues as means of transport between JD (Job Driver) and JP (Job Process). Instead, each JP uses HTTP to request a Work Item (CAS) from a JD.
DUCC 1.1.0 has a concept of a WI timeout which I think is 24 hours by default. A timer is started in a JD when each WI is dispatched to a JP. If the WI does not come back for whatever reason, the timer pops and a JD will attempt to retry that WI. To debug your problem with DUCC 1.1.0 I suggest attaching JMX console to a running JP to see where its threads are. Before doing this, check JP logs to see if there is an exception. Jerry On Thu, Sep 17, 2015 at 4:32 AM, reshu.agarwal <reshu.agar...@orkash.com> wrote: > My DUCC version is 1.1.0. > > > On 09/17/2015 11:35 AM, reshu.agarwal wrote: > >> >> Hi, >> >> I am facing a problem in DUCC that some documents were shown in queue but >> did not get processed. In Job, work item list shows a particular work >> item's status "queued" and queueing time is "4115 seconds". >> >> I want to set queueing time of work item not more then 1 minute. What is >> the reason for the same? Is there any method to solve this? How can I set >> maximum queueing time for work item? >> >> Thanks in advance. >> >> Reshu. >> > >
