Return-Path: Delivered-To: apmail-uima-user-archive@www.apache.org Received: (qmail 2912 invoked from network); 12 May 2010 20:10:40 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 12 May 2010 20:10:40 -0000 Received: (qmail 34755 invoked by uid 500); 12 May 2010 20:10:40 -0000 Delivered-To: apmail-uima-user-archive@uima.apache.org Received: (qmail 34712 invoked by uid 500); 12 May 2010 20:10:40 -0000 Mailing-List: contact user-help@uima.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@uima.apache.org Delivered-To: mailing list user@uima.apache.org Received: (qmail 34704 invoked by uid 99); 12 May 2010 20:10:40 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 12 May 2010 20:10:40 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of lally.adam@gmail.com designates 74.125.83.47 as permitted sender) Received: from [74.125.83.47] (HELO mail-gw0-f47.google.com) (74.125.83.47) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 12 May 2010 20:10:34 +0000 Received: by gwj15 with SMTP id 15so231110gwj.6 for ; Wed, 12 May 2010 13:10:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:received :in-reply-to:references:date:x-google-sender-auth:message-id:subject :from:to:content-type; bh=fbdJlKqyA0WZ16TUDjTjk1G8qLUxbOePGp+prrlLQ2A=; b=Y32SIvuxM7eCQ1Qvu2vriGzVvupLBl6m84422O5P7/YO2jKYMhW0GO7HCkCLLs6g0R krb+p3XlG6aacXp6fUAF34z/dQTRLSCWKLfiuLY/i6seMpraQCke2EJ8VTfvl4nW7C8S LKpToUAiEbgVdxiQ8LJkoOIHcTOyLKbZACodo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; b=LboG0zz3YPKHAlQrTP0+RVGjp4DFP316TP9x5uJHfIEO0u+T9xLJeui0Ykh32SLzv1 8EGIScpV6lu6SRepnUwR7GZXz8wRVn/j6mlnu0Be1Hg8SV08QkjCiyiZE+2K1QGQYtgG 5rT3Kg1erpzNIrXUROak1c0BpF0WvelMtI1TE= MIME-Version: 1.0 Received: by 10.91.82.17 with SMTP id j17mr2697965agl.40.1273695012427; Wed, 12 May 2010 13:10:12 -0700 (PDT) Sender: lally.adam@gmail.com Received: by 10.90.102.7 with HTTP; Wed, 12 May 2010 13:10:12 -0700 (PDT) In-Reply-To: References: Date: Wed, 12 May 2010 16:10:12 -0400 X-Google-Sender-Auth: kzoDMcO2b3MZguiP92550GAf2hc Message-ID: Subject: Re: UIMA stops suddenly From: Adam Lally To: user@uima.apache.org Content-Type: multipart/alternative; boundary=001485f9460ac4995f04866b3a61 X-Virus-Checked: Checked by ClamAV on apache.org --001485f9460ac4995f04866b3a61 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On Wed, May 12, 2010 at 2:42 PM, Radwen Aniba wrote: > it is very possible that an annotator hang (since a treatement could be > long > to do) and if this is the case is there a way to let him hang anyway ? Wh= y > an annotator stops when it takes a while treating a document ? > It doesn't stop. By "hang" I meant your annotator could be taking *forever*, or at least such a long time that you were not willing to wait for it. -Adam > > 2010/5/12 Adam Lally > > > On Wed, May 12, 2010 at 1:35 PM, Eddie Epstein > > wrote: > > > > > It is possible that the user's annotator code is hanging. Either add > > > code to trace the annotator entry and exit, or turn on UIMA logging a= t > > > level FINE to see what the last thing being done is. > > > > > > Eddie > > > > > > On Wed, May 12, 2010 at 5:41 AM, Radwen Aniba > wrote: > > > > Hi everybodey, > > > > > > > > I developped an application using UIMA and while running it on a bi= g > > set > > > of > > > > documents which takes some time to process, UIMA suddenly stops > without > > > any > > > > error message or warning > > > > > > > > Is there anything I can do to know where the problem occur ? > > > > > > > > Thanks for help > > > > > > > > Rad > > > > > > > > -- > > > > > > > > > > > There's a convenient utility called jstack that comes with Java that le= ts > > you examine the stack track of any running process. See > > http://java.sun.com/j2se/1.5.0/docs/tooldocs/share/jstack.html > > > > By looking at the stack traces you should be able to tell if any of the= m > > are > > hung inside annotator code. > > > > -Adam > > > > > > -- > R. ANIBA > > Bioinformatics PhD > Laboratoire de Bioinformatique et G=E9nomique Int=E9gratives, > Institut de G=E9n=E9tique et de Biologie Mol=E9culaire et Cellulaire (IGB= MC), > 1 rue Laurent Fries, > 67404 Illkirch, France. > http://www-igbmc.u-strasbg.fr > http://alnitak.u-strasbg.fr/~aniba/alexsys > --001485f9460ac4995f04866b3a61--