Return-Path: Delivered-To: apmail-tomcat-users-archive@www.apache.org Received: (qmail 10675 invoked from network); 22 Jul 2010 14:38:12 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 22 Jul 2010 14:38:12 -0000 Received: (qmail 1903 invoked by uid 500); 22 Jul 2010 14:38:08 -0000 Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org Received: (qmail 1851 invoked by uid 500); 22 Jul 2010 14:38:08 -0000 Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Tomcat Users List" Delivered-To: mailing list users@tomcat.apache.org Received: (qmail 1841 invoked by uid 99); 22 Jul 2010 14:38:07 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 22 Jul 2010 14:38:07 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of aw@ice-sa.com designates 212.85.38.228 as permitted sender) Received: from [212.85.38.228] (HELO tor.combios.es) (212.85.38.228) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 22 Jul 2010 14:37:58 +0000 Received: from [192.168.245.235] (p549EA64E.dip0.t-ipconnect.de [84.158.166.78]) by tor.combios.es (Postfix) with ESMTPA id B454D226228 for ; Thu, 22 Jul 2010 16:35:35 +0200 (CEST) Message-ID: <4C48579B.7030207@ice-sa.com> Date: Thu, 22 Jul 2010 16:37:15 +0200 From: =?ISO-8859-1?Q?Andr=E9_Warnier?= Reply-To: Tomcat Users List User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) MIME-Version: 1.0 To: Tomcat Users List Subject: Re: Fire off asynch task in Tomcat. References: <4C47CFFD.1090603@gmail.com> <4C47F73D.9080707@ice-sa.com> <4C480262.4020707@ice-sa.com>,<4C480D17.10509@ceti.pl> <4C484E1F.5050501@ceti.pl> In-Reply-To: <4C484E1F.5050501@ceti.pl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Mikolaj Rydzewski wrote: > On 07/22/2010 03:49 PM, Martin Gainty wrote: >> //i wasnt able to determine JMX ability to schedule a specific task >> for a specific time? >> > > I was referring to Andre's sentence: > "[using database] makes it easier to suspend/resume the sending of > emails separately if you need to for some reason, without having to > change anything to your running webapp. " > > One can use JMX to interact with code running in (possibly even remote) > JVM. So, one can use JMX to stop/start sending emails, using custom code > of course. > And my point was (with laugh), that now it becomes interesting and > exciting feature to implement. > And I got the point, and appreciated it. :-) Maybe we should have a competition for whom can find the most exciting and complex solution to the OP's problem. I'm sure we could fit SOAP in there somewhere, and use Hadoop for the db back-end. ;-) --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org For additional commands, e-mail: users-help@tomcat.apache.org