uima-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Wahed Hemati <hem...@em.uni-frankfurt.de>
Subject Re: Run Job with deployment discriptor
Date Mon, 17 Oct 2016 19:38:43 GMT
Hi,

i let ducc now handle process_description_DD generation. Instead i 
specify process_descriptor_AE and process_descriptor_CC in my DuccJob 
and now it works. I think the problem was with my process_description_DD 
file. I'll digg a little deaper into that and will come back. Thanks alot

-Wahed


On 17.10.2016 21:31, Lou DeGenaro wrote:
> If it is not confidential and not too large can you zip up your user log
> directory comprising JD and JP (UIMA) logs and other related files and send
> to the mailing list as an attachment?  Or possibly post the zip file
> somewhere on a public drop site?
>
> Lou.
>
> On Mon, Oct 17, 2016 at 2:49 PM, Wahed Hemati <hemati@em.uni-frankfurt.de>
> wrote:
>
>> Hi,
>>
>> i get the following message:
>>
>> 17 Okt 2016 20:17:17,774  INFO JobProcessComponent - T[29] start  DUCC
>> Service Caught Kill Signal - Registering Killer Task and Stopping ...
>> 17 Okt 2016 20:18:17,776  INFO JobProcessComponent - T[59] start  Process
>> is about to kill itself via Runtime.getRuntime().halt()
>>
>>
>> I cant seem to find anything related to the error in the other logfiles.
>>
>> -Wahed
>>
>>
>> On 14.10.2016 18:54, Lou DeGenaro wrote:
>>
>>> Are there any clues in your log files?
>>>
>>> log_directory                   ${DUCC_HOME}/ducctest/logs
>>>
>>> Lou.
>>>
>>> On Fri, Oct 14, 2016 at 12:01 PM, Wahed Hemati <
>>> hemati@em.uni-frankfurt.de>
>>> wrote:
>>>
>>> Hi,
>>>> I want to run a Job with a deployment discriptor.
>>>>
>>>> My Job file looks like this:
>>>> description                     DUCC raw text sample application
>>>> driver_descriptor_CR de.tudarmstadt.ukp.dkpro.core.io.text.TextReader
>>>> process_descriptor_DD /home/ducc/ducc/ducctest/asJob
>>>> /deploymentdescriptr.xml
>>>> service_dependency UIMA-AS:BreakIteratorSegmenter:tcp://alba:61617
>>>> process_memory_size             1
>>>> process_pipeline_count          2
>>>> process_jvm_args                -Xmx3G -XX:+UseCompressedOops
>>>> -Djava.util.logging.config.file=/home/ducc/Desktop/ducctest/
>>>> ConsoleLogger.properties
>>>> scheduling_class                normal
>>>> working_directory               ${DUCC_HOME}/ducctest
>>>> log_directory                   ${DUCC_HOME}/ducctest/logs
>>>> process_per_item_time_max       10
>>>> classpath ${DUCC_HOME}/lib/uima-ducc/examples/*:${DUCC_HOME}/apache-
>>>> uima/lib/*:${DUCC_HOME}/apache-uima/apache-activemq/li
>>>> b/*:${DUCC_HOME}/apache-uima/apache-activemq/lib/optional/*:${DUCC_$
>>>> driver_descriptor_CR_overrides sourceLocation=${DUCC_HOME}/du
>>>> cctest/Books
>>>> patterns=[+]**/*.txt
>>>> wait_for_completion
>>>> cancel_on_interrupt
>>>> attach_console
>>>> debug
>>>>
>>>> my process_descriptor_DD looks like this:
>>>>
>>>> <?xml version="1.0" encoding="UTF-8"?>
>>>>
>>>> <analysisEngineDeploymentDescription xmlns="http://uima.apache.org/
>>>> resourceSpecifier">
>>>>     <name>tmp1476430573219</name>
>>>>     <version>2.0</version>
>>>>     <deployment protocol="jms" provider="activemq">
>>>>       <service>
>>>>         <inputQueue endpoint="de_______BreakIteratorSegmenter"
>>>> brokerURL="tcp://alba:61617" prefetch="0"/>
>>>>         <topDescriptor>
>>>>           <import location="/home/ducc/ducc/ducc
>>>> test/asJob/descriptor.xml"/>
>>>>         </topDescriptor>
>>>>         <analysisEngine>
>>>>           <delegates>
>>>>             <remoteAnalysisEngine key="BreakIteratorSegmenter">
>>>>               <inputQueue brokerURL="tcp://alba:61617"
>>>> endpoint="BreakIteratorSegmenter"/>
>>>>               <serializer method="xmi"/>
>>>>             </remoteAnalysisEngine>
>>>>           </delegates>
>>>>         </analysisEngine>
>>>>       </service>
>>>>     </deployment>
>>>> </analysisEngineDeploymentDescription>
>>>>
>>>>
>>>> When i ducc_submit the job, it gets stuck during Initializing.
>>>> Thanks in advance
>>>>
>>>> -Wahed
>>>>
>>>>
>>>>
>> --
>> A. Wahed Hemati
>> Text-Technology Lab
>> Fakultät für Informatik und Mathematik
>> Johann Wolfgang Goethe-Universität Frankfurt am Main
>> Senckenberganlage 31
>> 60325 Frankfurt am Main
>> Tel: +49 69-798-24662
>> Email: hemati@em.uni-frankfurt.de
>> Web: http://www.hucompute.org/
>>
>>


Mime
View raw message