Return-Path: X-Original-To: apmail-commons-user-archive@www.apache.org Delivered-To: apmail-commons-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 267A765A7 for ; Thu, 21 Jul 2011 11:30:36 +0000 (UTC) Received: (qmail 87601 invoked by uid 500); 21 Jul 2011 11:30:34 -0000 Delivered-To: apmail-commons-user-archive@commons.apache.org Received: (qmail 87106 invoked by uid 500); 21 Jul 2011 11:30:31 -0000 Mailing-List: contact user-help@commons.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Commons Users List" Delivered-To: mailing list user@commons.apache.org Received: (qmail 87095 invoked by uid 99); 21 Jul 2011 11:30:29 -0000 Received: from minotaur.apache.org (HELO minotaur.apache.org) (140.211.11.9) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 21 Jul 2011 11:30:29 +0000 Received: from localhost (HELO fc14x86v0.jboss.hr) (127.0.0.1) (smtp-auth username mturk, mechanism plain) by minotaur.apache.org (qpsmtpd/0.29) with ESMTP; Thu, 21 Jul 2011 11:30:29 +0000 Message-ID: <4E280DD0.3070409@apache.org> Date: Thu, 21 Jul 2011 13:30:24 +0200 From: Mladen Turk User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.18) Gecko/20110621 Fedora/3.1.11-1.fc14 Lightning/1.0b2 Thunderbird/3.1.11 MIME-Version: 1.0 To: user@commons.apache.org Subject: Re: [daemon] References: <4E204F13.8060400@apache.org> <4E2406AC.60201@apache.org> <4E245112.7060703@apache.org> <4E255FD1.2010309@apache.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit On 07/21/2011 08:58 AM, Hans Rupp wrote: > 2011/7/19 Mladen Turk > >> >> Well, write an ant task and start your application via ant. >> This is the first thing that comes to my mind. >> Or write you own simple class that will exec new jvm and >> monitor it's exit value. >> >> Thanks again, but i'm not familiar with ant and don't how to write a task > that can permanently monitor my application. So you are out of luck then ;) > I think your second suggestion isn't realy a solution, what should i do if > the monitoring jvm crashes? That's why its called "monitoring" it doesn't do any job except checking if the child is alive, and if not restart it according to some rules. People even write this kind of layer for standard services, because your application can become unresponsive without crashing the JVM. Also if you think your application could crash the JVM your are in much bigger problem. I think your entire use case is sort of an oxymoron. You wish a full blown service (like you've said "os-layer") and still to have the userland GUI. Split those two parts and use the IPC for communication between them. Regards -- ^TM --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscribe@commons.apache.org For additional commands, e-mail: user-help@commons.apache.org