From users-return-218035-apmail-tomcat-users-archive=tomcat.apache.org@tomcat.apache.org Fri Oct 15 15:46:31 2010 Return-Path: Delivered-To: apmail-tomcat-users-archive@www.apache.org Received: (qmail 30893 invoked from network); 15 Oct 2010 15:46:31 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 15 Oct 2010 15:46:31 -0000 Received: (qmail 11230 invoked by uid 500); 15 Oct 2010 15:46:27 -0000 Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org Received: (qmail 11033 invoked by uid 500); 15 Oct 2010 15:46:26 -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 11024 invoked by uid 99); 15 Oct 2010 15:46:26 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 15 Oct 2010 15:46:26 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [217.76.105.194] (HELO mx.business-code.de) (217.76.105.194) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 15 Oct 2010 15:46:20 +0000 Received: from localhost (localhost [127.0.0.1]) by mx.business-code.de (Postfix) with ESMTP id 56A922FAD5; Fri, 15 Oct 2010 17:45:58 +0200 (CEST) Received: from mx.business-code.de ([127.0.0.1]) by localhost (mx.business-code.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 09380-03; Fri, 15 Oct 2010 17:45:57 +0200 (CEST) Received: from lienen.business-code.de (lienen.business-code.de [192.168.10.1]) by mx.business-code.de (Postfix) with ESMTP id D40B12FA15 for ; Fri, 15 Oct 2010 17:45:57 +0200 (CEST) Received: from [192.168.11.53] (sanogo.business-code.de [192.168.11.53]) by lienen.business-code.de (Postfix) with ESMTP id 955031094EB for ; Fri, 15 Oct 2010 17:45:57 +0200 (CEST) Message-ID: <4CB87735.1060300@business-code.de> Date: Fri, 15 Oct 2010 17:45:57 +0200 From: =?ISO-8859-15?Q?Michael_Kn=FCmann?= User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9.2.9) Gecko/20100915 Lightning/1.0b2 Thunderbird/3.1.4 MIME-Version: 1.0 To: Tomcat Users List Subject: What is the lifecycle of the apache tribes channel? References: <20101015080212.GC11111@c3po> <32807776.111.1287138850583.JavaMail.tomcat@localhost> <20101015110033.GD11111@c3po> In-Reply-To: <20101015110033.GD11111@c3po> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at business-code.de Hi, I'm using apache tribes for messaging between nodes within a cluster. My implementation bases on the quickstart example that is part of the related documentation. At the moment there is Context Listener that starts the communication like this: myChannel = new GroupChannel(); this.msgListener = msgListener; this.mbrListener = mbrListener; //attach the listeners to the channel myChannel.addMembershipListener(mbrListener); myChannel.addChannelListener(msgListener); //start the channel myChannel.start(Channel.DEFAULT); This is a singleton instance and is used for sending messages the whole lifecycle of my webapplication. I don't like this singleton and I'm wondering if it is possible to start the channel everytime I need to send a message? with kind regards Michael --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org For additional commands, e-mail: users-help@tomcat.apache.org