Re: Infinte initialization of a process even after restarting DUCC
On 07/09/2014 03:25 PM, Lou DeGenaro wrote: Upon re-start (presuming you used the default warm start) all previous running jobs are marked as Completed. If the the job itself is Completed yet the job-processes continue to show an active state then this is erroneous information.. Dear Lou, The Job status in jobs is completed, but in the job processes ,there are 3 processes in which one is showing status Stopped, one is showing status Stopped but Time Run is increasing(2:15:59:40) and in one process status is starting and Time init is increasing(2:15:29:40). So, Job State Time Init Time Run Starting2:15:29:4000 Stopped00 2:15:59:40 So, Job is completed but still running. So, This is a bug which needs to resolve. -- Thanks, Reshu Agarwal
Re: Infinte initialization of a process even after restarting DUCC
The facts are: 1. The job is not really running. In reality there are *no* active job-processes. 2. The information on the Job Details page is wrong. It reports job-processes as running when in reality there are none. For example, can you find the PID for the supposedly running job-process on the machine where is the DUCC Web Server claims it to be running? My advise for the short term is: don't believe the Job Details page if the Jobs page says the job is Completed. Please open a Jira and I'll test and fix the faulty reporting by the Web Server (if not already fixed in the upcoming DUCC release). Lou. On Wed, Jul 9, 2014 at 7:12 AM, reshu.agarwal reshu.agar...@orkash.com wrote: On 07/09/2014 03:25 PM, Lou DeGenaro wrote: Upon re-start (presuming you used the default warm start) all previous running jobs are marked as Completed. If the the job itself is Completed yet the job-processes continue to show an active state then this is erroneous information.. Dear Lou, The Job status in jobs is completed, but in the job processes ,there are 3 processes in which one is showing status Stopped, one is showing status Stopped but Time Run is increasing(2:15:59:40) and in one process status is starting and Time init is increasing(2:15:29:40). So, Job State Time Init Time Run Starting2:15:29:4000 Stopped00 2:15:59:40 So, Job is completed but still running. So, This is a bug which needs to resolve. -- Thanks, Reshu Agarwal
Re: Read file name in an annotator
Hi Debbie, The file name is not provided by default in UIMA although I believe the UIMA FileReader does populate a SourceDocumentInformation annotation with this information. Our group has a set of readers that populate our own annotation type to provide location data and other meta-information for each record (CAS) being processed. In short you will be better off writing your reader to provide that information for you. Thanks, Thomas Ginter 801-448-7676 thomas.gin...@utah.edu On Jul 9, 2014, at 5:41, Debbie Zhang debbie.d.zh...@gmail.com wrote: Hi, Can anyone tell me how to read the file name in an annotator using the JCas? It seems the DocumentAnnotation does't contain file name. Thank you! Best regards, Debbie Zhang
