Hi Reshu, Each DUCC machine has an agent responsible for starting and killing processes. There was a bug ( https://issues.apache.org/jira/browse/UIMA-4194 ) where the agent failed to issue a kill -9 against "hung" JPs when a job was stopping. The fix is in v2.0.
Regards, Eddie On Tue, Jan 5, 2016 at 12:54 AM, reshu.agarwal <reshu.agar...@orkash.com> wrote: > I forget to mention one thing i.e. After Killing the job, next job is > unable to initialize and remain in " WaitingForDriver" state. I have also > checked sm.log,or.log,pm.log e.t.c. but failed to find any thing. I have to > restart my DUCC for running job again. > > Reshu. > > > On 01/05/2016 11:14 AM, reshu.agarwal wrote: > >> Hi, >> >> I am using DUCC 1.1.0 version. I am facing a issue with my job i.e. it >> remains in completing state even after initializing the stop process. My >> job used two processes. And Job Driver logs: >> >> Jan 04, 2016 12:43:13 PM >> org.apache.uima.adapter.jms.client.BaseUIMAAsynchronousEngineCommon_impl >> stop >> INFO: Stopping Asynchronous Client. >> Jan 04, 2016 12:43:13 PM >> org.apache.uima.adapter.jms.client.BaseUIMAAsynchronousEngineCommon_impl >> stop >> INFO: Asynchronous Client Has Stopped. >> Jan 04, 2016 12:43:13 PM >> org.apache.uima.adapter.jms.client.BaseUIMAAsynchronousEngineCommon_impl$SharedConnection >> destroy >> INFO: UIMA AS Client Shared Connection Has Been Closed >> Jan 04, 2016 12:43:13 PM >> org.apache.uima.adapter.jms.client.BaseUIMAAsynchronousEngine_impl stop >> INFO: UIMA AS Client Undeployed All Containers >> >> One process logs: >> >> Jan 04, 2016 12:44:50 PM >> org.apache.uima.adapter.jms.activemq.JmsInputChannel stopChannel >> INFO: Stopping Service JMS Transport. Service: ducc.jd.queue.87494 >> ShutdownNow false >> Jan 04, 2016 12:44:50 PM >> org.apache.uima.adapter.jms.activemq.JmsInputChannel stopChannel >> INFO: Controller: ducc.jd.queue.87494 Stopped Listener on Endpoint: >> queue://ducc.jd.queue.87494 Selector: Selector:Command=2000 OR Command=2002. >> >> But, other process do not have any log of stopping the process. >> >> The case is of not completely undeploying all processes. I have to use >> command to cancel the process: /ducc_install/bin$ ./ducc_cancel --id 87494 >> --dpid 4529. >> >> Some times it cancelled the process otherwise I have to use "kill -9" >> command to kill the job forcefully. >> >> Kindly help. >> >> Thanks in advanced. >> >> Reshu. >> >> >> >
