Hello All, I'm not sure if this belongs in dev because DUCC isn't released yet, but it feels like a user question.
I have modeled a CasReader and CasMultiplier based on the RawTextExample in the duccbook, and have successfully ran the CR and CM in eclipse with a minimal wrapper. I am using the same CC from the Sample (DuccCasCC) I am experiencing a problem where my DUCC job goes through WaitingForDriver, WaitingForResources, then Initializing, then doesn't change state. After several minutes I just cancel the job. The jd-out.log loops the following: 13 Nov 2013 13:47:02,966 11 DEBUG client.CasSource init 90 CR creation... 13 Nov 2013 13:47:03,706 11 DEBUG client.CasSource init 90 CR created. 13 Nov 2013 13:47:03,706 11 DEBUG jd.JobDriver initialize 90 CAS source initialized 13 Nov 2013 13:47:03,707 30 WARN jd.JobDriver run 90 no work items to process 13 Nov 2013 13:47:03,707 30 DEBUG jd.JobDriver run 90 thread processing complete 13 Nov 2013 13:47:09,092 12 DEBUG jd.JobDriverComponent getState N/A publishing state 13 Nov 2013 13:47:09,121 12 DEBUG jd.JobDriverComponent getState N/A driverState:Initializing 13 Nov 2013 13:47:09,121 12 DEBUG jd.JobDriverComponent getState 90 state:Initializing threads:0 total:-1 fetched:0 started:0 completed:0 error:0 lost:0 queued:0 in-progress:0 pending:true unassigned:0 retry:0 13 Nov 2013 13:47:12,304 11 DEBUG jd.JobDriverComponent evaluateDispatchedJobConstraints N/A received:OrchestratorStateEvent 13 Nov 2013 13:47:22,310 11 DEBUG jd.JobDriverComponent evaluateDispatchedJobConstraints N/A received:OrchestratorStateEvent 13 Nov 2013 13:47:24,091 12 DEBUG jd.JobDriverComponent getState N/A publishing state 13 Nov 2013 13:47:24,103 12 DEBUG jd.JobDriverComponent getState N/A driverState:Initializing 13 Nov 2013 13:47:24,103 12 DEBUG jd.JobDriverComponent getState 90 state:Initializing threads:0 total:-1 fetched:0 started:0 completed:0 error:0 lost:0 queued:0 in-progress:0 pending:true unassigned:0 retry:0 13 Nov 2013 13:47:32,304 11 DEBUG jd.JobDriverComponent evaluateDispatchedJobConstraints N/A received:OrchestratorStateEvent 13 Nov 2013 13:47:39,092 12 DEBUG jd.JobDriverComponent getState N/A publishing state 13 Nov 2013 13:47:39,106 12 DEBUG jd.JobDriverComponent getState N/A driverState:Initializing 13 Nov 2013 13:47:39,106 12 DEBUG jd.JobDriverComponent getState 90 state:Initializing threads:0 total:-1 fetched:0 started:0 completed:0 error:0 lost:0 queued:0 in-progress:0 pending:true unassigned:0 retry:0 .... Repeat. My Cas Reader and Cas Multiplier have initialized, because I get logging output from those functions. I don't see logging output of the CM's process() method, or the CR's getNext(); I'm pulling CASes from a web service. So my CR initializes by querying the service and receiving a list of ids that go into a queue. On getNext(), I add a Workitem for each id, setting input source to the id. On the CM, the process() sets a private class varaible to the WorkItem Iterator, and next() graps the next Workitem, its id, sends a GET to the service, and builds a CAS from the response and returns it. Any thoughts on how to trouble shoot? Thanks! Neal
